Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4caf311be911f8b048787987645e0c6b31cc52d003871b933d02481287add8e3

Tx prefix hash: 00b902390e7f522b3edc80cd07c134b1442569b1ccf6ece5425d42ed5986a0d7
Tx public key: 6239d8bd8f83a0c70dd736e6c71937c0e6bde893ff288902eeee2e1bf039442e
Timestamp: 1724323019 Timestamp [UCT]: 2024-08-22 10:36:59 Age [y:d:h:m:s]: 01:079:09:37:08
Block: 1093407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315197 RingCT/type: yes/0
Extra: 016239d8bd8f83a0c70dd736e6c71937c0e6bde893ff288902eeee2e1bf039442e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c1b12b7701e6a73f399cda4d6deee0d1cc5895a481d15be378ac8fcc9eeb73c 0.600000000000 1568344 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": 1093417, "vin": [ { "gen": { "height": 1093407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c1b12b7701e6a73f399cda4d6deee0d1cc5895a481d15be378ac8fcc9eeb73c" } } ], "extra": [ 1, 98, 57, 216, 189, 143, 131, 160, 199, 13, 215, 54, 230, 199, 25, 55, 192, 230, 189, 232, 147, 255, 40, 137, 2, 238, 238, 46, 27, 240, 57, 68, 46, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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