Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14f3f06a972ea16ea99a288a1eafbba730c581ba4b6629545f37dcb17a850af2

Tx prefix hash: dd5671e72567bb94e20b7c48cb65abe06e4c98e298659bf9df502d86d4895612
Tx public key: ddbef64104f1c7a8babeef6ba0209450f035895dc53cf0664b284760e302c0a3
Timestamp: 1696949508 Timestamp [UCT]: 2023-10-10 14:51:48 Age [y:d:h:m:s]: 01:160:19:59:02
Block: 866668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375987 RingCT/type: yes/0
Extra: 01ddbef64104f1c7a8babeef6ba0209450f035895dc53cf0664b284760e302c0a302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.824838981000 dcy

stealth address amount amount idx
00: 202a9257475519c9e4743b2a59f58d6318094dc15e871582b8dd4cadd30972aa 0.824838981000 1321290 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": 866678, "vin": [ { "gen": { "height": 866668 } } ], "vout": [ { "amount": 824838981, "target": { "key": "202a9257475519c9e4743b2a59f58d6318094dc15e871582b8dd4cadd30972aa" } } ], "extra": [ 1, 221, 190, 246, 65, 4, 241, 199, 168, 186, 190, 239, 107, 160, 32, 148, 80, 240, 53, 137, 93, 197, 60, 240, 102, 75, 40, 71, 96, 227, 2, 192, 163, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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