Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d5429cb7273b96ede786ccb2169d206daec7e2890e544bf47c7505ae25ef39

Tx prefix hash: 6b74783e43c3f837d5a877cebfa9a2882d56b3330e21506612f6e3901ae4a076
Tx public key: 02aa7d81d73d4e3145fc245c8e9e45edafadb887315eb5fbf8af0aa1af993cb6
Timestamp: 1755984840 Timestamp [UCT]: 2025-08-23 21:34:00 Age [y:d:h:m:s]: 00:089:17:26:55
Block: 1352966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64054 RingCT/type: yes/0
Extra: 0102aa7d81d73d4e3145fc245c8e9e45edafadb887315eb5fbf8af0aa1af993cb60211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caba107b226399c624fea06c26f26cd44262f5a364d1ab462653c3ebc90b0233 0.600000000000 1840935 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": 1352976, "vin": [ { "gen": { "height": 1352966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caba107b226399c624fea06c26f26cd44262f5a364d1ab462653c3ebc90b0233" } } ], "extra": [ 1, 2, 170, 125, 129, 215, 61, 78, 49, 69, 252, 36, 92, 142, 158, 69, 237, 175, 173, 184, 135, 49, 94, 181, 251, 248, 175, 10, 161, 175, 153, 60, 182, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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