Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b77ddb1d310fee3149b77b7bb5ee8151b323af8dfedd72e517ccfd935261d3d2

Tx prefix hash: bbe7463a52afd79d798a3eac832a6083fa8feab703062f8d4714af842fb39ef8
Tx public key: f4a3c7d86650c4d2d56264ef117218a59e7d59c49c3802a103effafe91f51de5
Timestamp: 1762156258 Timestamp [UCT]: 2025-11-03 07:50:58 Age [y:d:h:m:s]: 00:015:03:57:45
Block: 1403919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10874 RingCT/type: yes/0
Extra: 01f4a3c7d86650c4d2d56264ef117218a59e7d59c49c3802a103effafe91f51de502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5be5230d716e1db49b1d901df5dc537bfc2094a697d99123b1945d9a1c3809e8 0.600000000000 1892272 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": 1403929, "vin": [ { "gen": { "height": 1403919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5be5230d716e1db49b1d901df5dc537bfc2094a697d99123b1945d9a1c3809e8" } } ], "extra": [ 1, 244, 163, 199, 216, 102, 80, 196, 210, 213, 98, 100, 239, 17, 114, 24, 165, 158, 125, 89, 196, 156, 56, 2, 161, 3, 239, 250, 254, 145, 245, 29, 229, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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