Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d5c8bc29fa241a78b31aa9fcbe0a8cf088d2a8839299f9700132d7ab2556db8

Tx prefix hash: 838883f9a02bb95984eb9dd6cf3d71ad75e04bfe5f2668517d51e8697495ea44
Tx public key: 647bde5f9e0b0f0821046d684ced9383038c376a778071afe8597c5bd6cfa83d
Timestamp: 1709977317 Timestamp [UCT]: 2024-03-09 09:41:57 Age [y:d:h:m:s]: 01:029:07:52:46
Block: 974471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281939 RingCT/type: yes/0
Extra: 01647bde5f9e0b0f0821046d684ced9383038c376a778071afe8597c5bd6cfa83d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8779ab150f0fa877aae4a84984e6b2cbdf6ecd1fab4be5f6ea9669b226734c9b 0.600000000000 1434428 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": 974481, "vin": [ { "gen": { "height": 974471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8779ab150f0fa877aae4a84984e6b2cbdf6ecd1fab4be5f6ea9669b226734c9b" } } ], "extra": [ 1, 100, 123, 222, 95, 158, 11, 15, 8, 33, 4, 109, 104, 76, 237, 147, 131, 3, 140, 55, 106, 119, 128, 113, 175, 232, 89, 124, 91, 214, 207, 168, 61, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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