Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969baf8f178080a5a7dc015eaf99ea51874d519615c7289bbdd764c2f55cc682

Tx prefix hash: e41b4c8add5c465aec1c7cc35b06cb3336cc47a637b8cf97066328d6a7c07223
Tx public key: 226f07ae055cc0b19241f8dbf79621a989e8bdf0f3cfc0f65e6e4de782701d6c
Timestamp: 1703704294 Timestamp [UCT]: 2023-12-27 19:11:34 Age [y:d:h:m:s]: 01:112:14:19:03
Block: 922462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341594 RingCT/type: yes/0
Extra: 01226f07ae055cc0b19241f8dbf79621a989e8bdf0f3cfc0f65e6e4de782701d6c02110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b620b567d8866cf5e29efc7065be9fd60e4c846b6c7419552faa8d19c9143b97 0.600000000000 1380160 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": 922472, "vin": [ { "gen": { "height": 922462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b620b567d8866cf5e29efc7065be9fd60e4c846b6c7419552faa8d19c9143b97" } } ], "extra": [ 1, 34, 111, 7, 174, 5, 92, 192, 177, 146, 65, 248, 219, 247, 150, 33, 169, 137, 232, 189, 240, 243, 207, 192, 246, 94, 110, 77, 231, 130, 112, 29, 108, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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