Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9ce0e8796ff6edb3aa1afe02e893ff66aba6929fb75ee85f6677a443f73e4b

Tx prefix hash: 76bd313268450310886f96bbc69953fbb6b745d78ebfee14d56dd06b209a4abc
Tx public key: fae3e71b4c7ba2d90bd3e53d78b367c04500f834c17c6f2baae33a4f5324bbbf
Timestamp: 1738031817 Timestamp [UCT]: 2025-01-28 02:36:57 Age [y:d:h:m:s]: 00:327:05:29:01
Block: 1206641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231670 RingCT/type: yes/0
Extra: 01fae3e71b4c7ba2d90bd3e53d78b367c04500f834c17c6f2baae33a4f5324bbbf0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 771df789978b0b6830fbf901d0d16607361bc56c7f59593b172eb4d42965b801 0.600000000000 1693352 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": 1206651, "vin": [ { "gen": { "height": 1206641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "771df789978b0b6830fbf901d0d16607361bc56c7f59593b172eb4d42965b801" } } ], "extra": [ 1, 250, 227, 231, 27, 76, 123, 162, 217, 11, 211, 229, 61, 120, 179, 103, 192, 69, 0, 248, 52, 193, 124, 111, 43, 170, 227, 58, 79, 83, 36, 187, 191, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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