Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d8009710b72da709e2fbf4b6e727b0aac691c7fd4321c5185cc10a8bf0ca097

Tx prefix hash: 061fec094639ecc6f7db094945c5130bd0f146b9e29b6145f20dbeb58a8cbe3c
Tx public key: f7850a561a4c720ef80c89d82b9e6e29479b4c7577dbf1892f6d2dce53db95c4
Timestamp: 1750115773 Timestamp [UCT]: 2025-06-16 23:16:13 Age [y:d:h:m:s]: 00:151:00:52:18
Block: 1306555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105738 RingCT/type: yes/0
Extra: 01f7850a561a4c720ef80c89d82b9e6e29479b4c7577dbf1892f6d2dce53db95c4021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b511a87fdaacf0a8479acda6847ca54ebf8ee52402d61ecb30a2d68819c46586 0.600000000000 1794162 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": 1306565, "vin": [ { "gen": { "height": 1306555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b511a87fdaacf0a8479acda6847ca54ebf8ee52402d61ecb30a2d68819c46586" } } ], "extra": [ 1, 247, 133, 10, 86, 26, 76, 114, 14, 248, 12, 137, 216, 43, 158, 110, 41, 71, 155, 76, 117, 119, 219, 241, 137, 47, 109, 45, 206, 83, 219, 149, 196, 2, 17, 0, 0, 0, 5, 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