Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5bb43bac47ee3927025365c7137056ee45367b7f418a3cd6b0afa744a3dcf8

Tx prefix hash: 1d18a88348a29cc9fc5feeac63dc217db225bce2333587c73e5a0e625cda3340
Tx public key: fff2d0caedd5c97f483b266a1a860ad5e2bc0b41cb59d0477f612144f39d95f5
Timestamp: 1751673744 Timestamp [UCT]: 2025-07-05 00:02:24 Age [y:d:h:m:s]: 00:131:23:55:51
Block: 1318910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92667 RingCT/type: yes/0
Extra: 01fff2d0caedd5c97f483b266a1a860ad5e2bc0b41cb59d0477f612144f39d95f50211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aec6c9aea0eec4eb72ef14f6c64c18c77483cf33762ca0d0aba7e9d38711dd4 0.600000000000 1806597 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": 1318920, "vin": [ { "gen": { "height": 1318910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aec6c9aea0eec4eb72ef14f6c64c18c77483cf33762ca0d0aba7e9d38711dd4" } } ], "extra": [ 1, 255, 242, 208, 202, 237, 213, 201, 127, 72, 59, 38, 106, 26, 134, 10, 213, 226, 188, 11, 65, 203, 89, 208, 71, 127, 97, 33, 68, 243, 157, 149, 245, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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