Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 284b8564d69a35ef6428436e78b25aadd0164886d7532b417f889d184f2b9f7c

Tx prefix hash: bbe3ac63599594bd29b216d0b297bfc4911992d0042506463c0c84b493cd4b23
Tx public key: 22d22f2c1edf550f92b1e82a0b35b531c5388b8d70031feb60cedac2a735c6e6
Timestamp: 1748886556 Timestamp [UCT]: 2025-06-02 17:49:16 Age [y:d:h:m:s]: 00:236:17:19:06
Block: 1296497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166771 RingCT/type: yes/0
Extra: 0122d22f2c1edf550f92b1e82a0b35b531c5388b8d70031feb60cedac2a735c6e6021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d9a5b9cd8abb1d90810f906c70b5288bf25846361dd3e03fdf84becf1115698 0.600000000000 1784008 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": 1296507, "vin": [ { "gen": { "height": 1296497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d9a5b9cd8abb1d90810f906c70b5288bf25846361dd3e03fdf84becf1115698" } } ], "extra": [ 1, 34, 210, 47, 44, 30, 223, 85, 15, 146, 177, 232, 42, 11, 53, 181, 49, 197, 56, 139, 141, 112, 3, 31, 235, 96, 206, 218, 194, 167, 53, 198, 230, 2, 17, 0, 0, 0, 9, 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