Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5b709a6585d607a701caae584e6ca61191efabbb353226d7b3dfd00cf90d5b3

Tx prefix hash: 5a61914ceb5fb839f454b77670417c9302b20fec71faf95370d0e5474355fe8f
Tx public key: 0fb5fa5ab068b50d762c45f3cd8defd450800b6aa88e9bb0b3e6de8b83bb3703
Timestamp: 1750161373 Timestamp [UCT]: 2025-06-17 11:56:13 Age [y:d:h:m:s]: 00:155:14:19:11
Block: 1306943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108994 RingCT/type: yes/0
Extra: 010fb5fa5ab068b50d762c45f3cd8defd450800b6aa88e9bb0b3e6de8b83bb3703021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d3c5e8a467d48b5db2d3a7c8fc6c0a3a66a2deddf18a295f8456fcff7170bb1 0.600000000000 1794552 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": 1306953, "vin": [ { "gen": { "height": 1306943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3c5e8a467d48b5db2d3a7c8fc6c0a3a66a2deddf18a295f8456fcff7170bb1" } } ], "extra": [ 1, 15, 181, 250, 90, 176, 104, 181, 13, 118, 44, 69, 243, 205, 141, 239, 212, 80, 128, 11, 106, 168, 142, 155, 176, 179, 230, 222, 139, 131, 187, 55, 3, 2, 17, 0, 0, 0, 2, 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