Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb1157431599d742c1b1946ad75f11f705af85f9448f3237b8cecfa256bcc76

Tx prefix hash: 801bd87eb5df57ae652abe7464f8c60603908af04d9761adf3d8b5e2ed3eeb42
Tx public key: 5fd896736aaf55e5ed80497f5bed58baf717d4c60f83738ab9cb0b0fe2c755d4
Timestamp: 1757792140 Timestamp [UCT]: 2025-09-13 19:35:40 Age [y:d:h:m:s]: 00:140:18:40:52
Block: 1367762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100619 RingCT/type: yes/0
Extra: 015fd896736aaf55e5ed80497f5bed58baf717d4c60f83738ab9cb0b0fe2c755d402110000000aad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b5f41c7de9f40dd9dd670d18dfe763bee94d8d0cda1b6b50b319adf2849bf31 0.600000000000 1855801 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": 1367772, "vin": [ { "gen": { "height": 1367762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b5f41c7de9f40dd9dd670d18dfe763bee94d8d0cda1b6b50b319adf2849bf31" } } ], "extra": [ 1, 95, 216, 150, 115, 106, 175, 85, 229, 237, 128, 73, 127, 91, 237, 88, 186, 247, 23, 212, 198, 15, 131, 115, 138, 185, 203, 11, 15, 226, 199, 85, 212, 2, 17, 0, 0, 0, 10, 173, 121, 72, 208, 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