Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9121e8b7d0f3fd13b9b3b8ce5defe17fb96a84727a60791a9b47f5f48f28f7cf

Tx prefix hash: 8d7499c0c4a9e8f5781fc96f7f4c4560ef8d0fd6b1a9b5986e9be6c6e6dbba5c
Tx public key: 0ed65b29c706cee3860af670f9a3b762d5f8684d745e14bfc0009609ddb819a2
Timestamp: 1648421533 Timestamp [UCT]: 2022-03-27 22:52:13 Age [y:d:h:m:s]: 02:098:02:03:33
Block: 467806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589476 RingCT/type: yes/0
Extra: 010ed65b29c706cee3860af670f9a3b762d5f8684d745e14bfc0009609ddb819a202110000001306faf294000000000000000000

1 output(s) for total of 17.296760786000 dcy

stealth address amount amount idx
00: 141ee53eea23e74f8ab08ddd426ff762ad214a7f7be322d9ed695ade89f46db2 17.296760786000 886383 of 0

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": 467816, "vin": [ { "gen": { "height": 467806 } } ], "vout": [ { "amount": 17296760786, "target": { "key": "141ee53eea23e74f8ab08ddd426ff762ad214a7f7be322d9ed695ade89f46db2" } } ], "extra": [ 1, 14, 214, 91, 41, 199, 6, 206, 227, 134, 10, 246, 112, 249, 163, 183, 98, 213, 248, 104, 77, 116, 94, 20, 191, 192, 0, 150, 9, 221, 184, 25, 162, 2, 17, 0, 0, 0, 19, 6, 250, 242, 148, 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