Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c74507040672c5d3ba602db507f3deeed0550b41d4841470aa828a5f2a9890

Tx prefix hash: e046eefd19ba760a8e8c505b60a00ca5cf87084c7274a28aea41260cc362881b
Tx public key: 1474c23e86e3ff4d5625ee892eb72c1e05d748403616756aef1b913b4a5ddad9
Timestamp: 1702967797 Timestamp [UCT]: 2023-12-19 06:36:37 Age [y:d:h:m:s]: 01:178:04:31:59
Block: 916364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388434 RingCT/type: yes/0
Extra: 011474c23e86e3ff4d5625ee892eb72c1e05d748403616756aef1b913b4a5ddad9021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0413fa0ea092b1ea3eea7d93f17e6131d1aaf54301b19daefdbe645fa9ea3f9 0.600000000000 1373864 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": 916374, "vin": [ { "gen": { "height": 916364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0413fa0ea092b1ea3eea7d93f17e6131d1aaf54301b19daefdbe645fa9ea3f9" } } ], "extra": [ 1, 20, 116, 194, 62, 134, 227, 255, 77, 86, 37, 238, 137, 46, 183, 44, 30, 5, 215, 72, 64, 54, 22, 117, 106, 239, 27, 145, 59, 74, 93, 218, 217, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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