Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1820aebe4d1c7c32ccc6e6312c60820a0d36be75440fef6fc57c664d76fb89d

Tx prefix hash: 4a8bc4b4cfd5fe7fab28ad12fb35dcf4a39c387dfabc388f1a1c14af9d71b29a
Tx public key: 95a60454f1fd3c6b4018123c68f02dba82121d5bb4b1125db5bf933bd72431f8
Timestamp: 1750496625 Timestamp [UCT]: 2025-06-21 09:03:45 Age [y:d:h:m:s]: 00:152:09:51:52
Block: 1309648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106779 RingCT/type: yes/0
Extra: 0195a60454f1fd3c6b4018123c68f02dba82121d5bb4b1125db5bf933bd72431f8021100000017bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b19f6b95e4d6226843c26fb496a1331d288ef03a34cb5d2fae7f0f41e34729bd 0.600000000000 1797265 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": 1309658, "vin": [ { "gen": { "height": 1309648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b19f6b95e4d6226843c26fb496a1331d288ef03a34cb5d2fae7f0f41e34729bd" } } ], "extra": [ 1, 149, 166, 4, 84, 241, 253, 60, 107, 64, 24, 18, 60, 104, 240, 45, 186, 130, 18, 29, 91, 180, 177, 18, 93, 181, 191, 147, 59, 215, 36, 49, 248, 2, 17, 0, 0, 0, 23, 191, 81, 178, 162, 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