Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 257eab642134d4208f4ea973465588d3b3d4505398fb10145917b4cdeb75133a

Tx prefix hash: 191b83591cbcb5048106f7f615c5c417daab15d81eedb8a3c12a1fd4cf8deb9d
Tx public key: 9171485a6ddd2e389901a4b1267e937bd3c63ad4856e18f992a84aa2b2db1cf4
Timestamp: 1763391721 Timestamp [UCT]: 2025-11-17 15:02:01 Age [y:d:h:m:s]: 00:076:23:54:42
Block: 1414167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54957 RingCT/type: yes/0
Extra: 019171485a6ddd2e389901a4b1267e937bd3c63ad4856e18f992a84aa2b2db1cf402110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e3f1eb315ea1328f9f4b2843debff850d8778d769662b6ebfab7a8bac9c1c94 0.600000000000 1902654 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": 1414177, "vin": [ { "gen": { "height": 1414167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e3f1eb315ea1328f9f4b2843debff850d8778d769662b6ebfab7a8bac9c1c94" } } ], "extra": [ 1, 145, 113, 72, 90, 109, 221, 46, 56, 153, 1, 164, 177, 38, 126, 147, 123, 211, 198, 58, 212, 133, 110, 24, 249, 146, 168, 74, 162, 178, 219, 28, 244, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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