Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d68dbc7fff230221dd662825cf5b6573c185c8c166d08f9634b37b6ff93a62

Tx prefix hash: f67dadcbcd912eec430e6a4ccf17c64b42760d9184c8928fc1ffb1893b96a775
Tx public key: 17e0a339f7b92e80e4be8a3bb52ccaf931a071f5d5f257c049f7d55729d6f5b3
Timestamp: 1685119574 Timestamp [UCT]: 2023-05-26 16:46:14 Age [y:d:h:m:s]: 01:327:11:58:48
Block: 768632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495273 RingCT/type: yes/0
Extra: 0117e0a339f7b92e80e4be8a3bb52ccaf931a071f5d5f257c049f7d55729d6f5b3021100000003b3164c24000000000000000000

1 output(s) for total of 1.742622373000 dcy

stealth address amount amount idx
00: a6b4a5f0b915bd5d1ea784ff31cb1f7a40982ac1418548bfd15e08a7a24ebf1e 1.742622373000 1217839 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": 768642, "vin": [ { "gen": { "height": 768632 } } ], "vout": [ { "amount": 1742622373, "target": { "key": "a6b4a5f0b915bd5d1ea784ff31cb1f7a40982ac1418548bfd15e08a7a24ebf1e" } } ], "extra": [ 1, 23, 224, 163, 57, 247, 185, 46, 128, 228, 190, 138, 59, 181, 44, 202, 249, 49, 160, 113, 245, 213, 242, 87, 192, 73, 247, 213, 87, 41, 214, 245, 179, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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