Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2b746940490bceff62f5b45063139e564334233ccb847bf79961015303ecc82

Tx prefix hash: 5d89fd40d7f045b847d88a03fd7ce77d0a6a53e223fe442672ed943b11ed338a
Tx public key: a694782b9ee9e4eefbf7851be0c6aefc34d2b28c8cad03779bc1321d8163a1eb
Timestamp: 1625014458 Timestamp [UCT]: 2021-06-30 00:54:18 Age [y:d:h:m:s]: 04:135:05:31:18
Block: 285563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124047 RingCT/type: yes/0
Extra: 01a694782b9ee9e4eefbf7851be0c6aefc34d2b28c8cad03779bc1321d8163a1eb021100000004b8178fc1000000000000000000

1 output(s) for total of 69.472311571000 dcy

stealth address amount amount idx
00: c4380fdb0c53068f2545e99fd0005d40f4b7a5c271db3094e230f87628d1786a 69.472311571000 597884 of 0

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": 285573, "vin": [ { "gen": { "height": 285563 } } ], "vout": [ { "amount": 69472311571, "target": { "key": "c4380fdb0c53068f2545e99fd0005d40f4b7a5c271db3094e230f87628d1786a" } } ], "extra": [ 1, 166, 148, 120, 43, 158, 233, 228, 238, 251, 247, 133, 27, 224, 198, 174, 252, 52, 210, 178, 140, 140, 173, 3, 119, 155, 193, 50, 29, 129, 99, 161, 235, 2, 17, 0, 0, 0, 4, 184, 23, 143, 193, 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