Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c23d5956ab40998e32be5debdc0204c647e357bc4c3f9a5374d0af65cc89d7

Tx prefix hash: edc9073735838c86ad0be4c4fa4c957c4c6a69d5a6df04a8e4cd9b678ede04ad
Tx public key: 6123689988194c01934d4eb153f0c7ec35b323d28d8876d91e2151c30a7c5ef8
Timestamp: 1724509561 Timestamp [UCT]: 2024-08-24 14:26:01 Age [y:d:h:m:s]: 00:202:15:39:19
Block: 1094971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144673 RingCT/type: yes/0
Extra: 016123689988194c01934d4eb153f0c7ec35b323d28d8876d91e2151c30a7c5ef8021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94d4c093761fb841ec3eb1fb4382d37358b5d488cfd7f6982cc9705ae59c0a2 0.600000000000 1570094 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": 1094981, "vin": [ { "gen": { "height": 1094971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94d4c093761fb841ec3eb1fb4382d37358b5d488cfd7f6982cc9705ae59c0a2" } } ], "extra": [ 1, 97, 35, 104, 153, 136, 25, 76, 1, 147, 77, 78, 177, 83, 240, 199, 236, 53, 179, 35, 210, 141, 136, 118, 217, 30, 33, 81, 195, 10, 124, 94, 248, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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