Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab6e1627a2118c11c59570fe7e45a12dec2fd358fb73b4f55b3723bb6826dd3a

Tx prefix hash: be8a4996ec249fcb58a55763ac8c0c2150f25a945ff36c9fd4391e107dfc5709
Tx public key: 2bb2e646c395984f621572eb264851ba5b654763d39d8d44dd074150ffe6f170
Timestamp: 1702341909 Timestamp [UCT]: 2023-12-12 00:45:09 Age [y:d:h:m:s]: 01:333:06:07:00
Block: 911163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497034 RingCT/type: yes/0
Extra: 012bb2e646c395984f621572eb264851ba5b654763d39d8d44dd074150ffe6f17002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c4a30a44295831c4a7da59b28b1051b70bd83b7f1c3acde401a6b8d5f7cbffb 0.600000000000 1368344 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": 911173, "vin": [ { "gen": { "height": 911163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c4a30a44295831c4a7da59b28b1051b70bd83b7f1c3acde401a6b8d5f7cbffb" } } ], "extra": [ 1, 43, 178, 230, 70, 195, 149, 152, 79, 98, 21, 114, 235, 38, 72, 81, 186, 91, 101, 71, 99, 211, 157, 141, 68, 221, 7, 65, 80, 255, 230, 241, 112, 2, 17, 0, 0, 0, 2, 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