Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff460b20c429bb88b0bc2c162b5dc437beb052959bb8e7eca1b82b5b9c8870ac

Tx prefix hash: 6a774052ee0a189d0b9257fd29b5a04eed84aa44f04e741a280f59fa43f42e88
Tx public key: e2fbd139575148e05c60aaa5eac5b2f7070d107e5842a72cf43d89ae57cefe25
Timestamp: 1704333366 Timestamp [UCT]: 2024-01-04 01:56:06 Age [y:d:h:m:s]: 01:160:01:42:08
Block: 927678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375506 RingCT/type: yes/0
Extra: 01e2fbd139575148e05c60aaa5eac5b2f7070d107e5842a72cf43d89ae57cefe2502110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1167c6b361798955c9fb1594b6bb5cfb75cecb22e00b979d9a3657b0f8d5d1d6 0.600000000000 1385514 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": 927688, "vin": [ { "gen": { "height": 927678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1167c6b361798955c9fb1594b6bb5cfb75cecb22e00b979d9a3657b0f8d5d1d6" } } ], "extra": [ 1, 226, 251, 209, 57, 87, 81, 72, 224, 92, 96, 170, 165, 234, 197, 178, 247, 7, 13, 16, 126, 88, 66, 167, 44, 244, 61, 137, 174, 87, 206, 254, 37, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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