Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48eb38a317b5b85eef29baaf24bd951a42d60c6aab5d1c2a58262adf8c27265

Tx prefix hash: 0e5f3b7314c98501fd5d28eb788f5a9852c91c971eb88685b6f34476bafa3c80
Tx public key: 68b8aaa9a59cb87488e318544cad3c077640cf9956e2d9d8f376344dbfcf33f2
Timestamp: 1732415084 Timestamp [UCT]: 2024-11-24 02:24:44 Age [y:d:h:m:s]: 00:121:16:11:41
Block: 1160392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86763 RingCT/type: yes/0
Extra: 0168b8aaa9a59cb87488e318544cad3c077640cf9956e2d9d8f376344dbfcf33f2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e4f8a2834ce42c46f2422c47ee3eaed940317adc43d609506dcb16a9ec0ce92 0.600000000000 1646039 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": 1160402, "vin": [ { "gen": { "height": 1160392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e4f8a2834ce42c46f2422c47ee3eaed940317adc43d609506dcb16a9ec0ce92" } } ], "extra": [ 1, 104, 184, 170, 169, 165, 156, 184, 116, 136, 227, 24, 84, 76, 173, 60, 7, 118, 64, 207, 153, 86, 226, 217, 216, 243, 118, 52, 77, 191, 207, 51, 242, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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