Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d1c2c6ed102362d9ac6eb66c5de92f7f6ab8ca4ec4f5cf91ac7547fbe84f180

Tx prefix hash: c2d8a81be84b88692051841af969338f4bda5eda2b377b485b453f66f6cdc53e
Tx public key: 9e84aa14b0fed20a1437e16430a2bc9b0dafa0128d6403dc0a54a18642f60c95
Timestamp: 1744531499 Timestamp [UCT]: 2025-04-13 08:04:59 Age [y:d:h:m:s]: 00:221:16:30:16
Block: 1260429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156156 RingCT/type: yes/0
Extra: 019e84aa14b0fed20a1437e16430a2bc9b0dafa0128d6403dc0a54a18642f60c950211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f664ed0ffd5899ffcb9067baaa1264f907b3063d8c54acbab1f33ad1ec9cd0cf 0.600000000000 1747586 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": 1260439, "vin": [ { "gen": { "height": 1260429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f664ed0ffd5899ffcb9067baaa1264f907b3063d8c54acbab1f33ad1ec9cd0cf" } } ], "extra": [ 1, 158, 132, 170, 20, 176, 254, 210, 10, 20, 55, 225, 100, 48, 162, 188, 155, 13, 175, 160, 18, 141, 100, 3, 220, 10, 84, 161, 134, 66, 246, 12, 149, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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