Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b252d0ba2a9ba5918d1a0f62eee2383198d9f47062ce13597c1ad33b59d87c2

Tx prefix hash: 9e9905697ccae39bbf2a43f499798dd035590b2ff20e578855238f9b5dc0d6fc
Tx public key: 5bede321231d46acb4f34e1bd7a548deeff550df06d5d6184e3385764b42efc3
Timestamp: 1746820085 Timestamp [UCT]: 2025-05-09 19:48:05 Age [y:d:h:m:s]: 00:196:03:36:16
Block: 1279373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137902 RingCT/type: yes/0
Extra: 015bede321231d46acb4f34e1bd7a548deeff550df06d5d6184e3385764b42efc30211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 391d2f312f4233830be63c75df47e2252bfeffecc89e02f30e8b1daa577575e3 0.600000000000 1766750 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": 1279383, "vin": [ { "gen": { "height": 1279373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "391d2f312f4233830be63c75df47e2252bfeffecc89e02f30e8b1daa577575e3" } } ], "extra": [ 1, 91, 237, 227, 33, 35, 29, 70, 172, 180, 243, 78, 27, 215, 165, 72, 222, 239, 245, 80, 223, 6, 213, 214, 24, 78, 51, 133, 118, 75, 66, 239, 195, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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