Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7019ae7a42791f7458ff982ad4da6c4d698078a782f7a03c6789091e9c443a21

Tx prefix hash: e7bc67b971f712cf36fb89eaff3ff9f161a79214a8b81ca0aedda013fea37313
Tx public key: 3fb43869926b7f750c93970fe8388e1a8d4049ab04a21e4c0f6158a56661dcce
Timestamp: 1749542121 Timestamp [UCT]: 2025-06-10 07:55:21 Age [y:d:h:m:s]: 00:152:20:16:52
Block: 1301912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106923 RingCT/type: yes/0
Extra: 013fb43869926b7f750c93970fe8388e1a8d4049ab04a21e4c0f6158a56661dcce02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b954f84b4d425d54b74068997dc7d02bcc03738067e784576adaeacc91f7cfbe 0.600000000000 1789475 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1301922, "vin": [ { "gen": { "height": 1301912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b954f84b4d425d54b74068997dc7d02bcc03738067e784576adaeacc91f7cfbe" } } ], "extra": [ 1, 63, 180, 56, 105, 146, 107, 127, 117, 12, 147, 151, 15, 232, 56, 142, 26, 141, 64, 73, 171, 4, 162, 30, 76, 15, 97, 88, 165, 102, 97, 220, 206, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8