Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17dc1fa71b288a4f15f10663070bd38809770cea29e9ab4a9aa25c13b8b2f77

Tx prefix hash: a04bdec2193297d5878e374472f6b11c7196dcd58a8da22d02598d62d29966b6
Tx public key: 73c78a7a0bea5e0ee246addd49afd4d766115b375d06dc8ed8ebd0fa3427a49c
Timestamp: 1702834888 Timestamp [UCT]: 2023-12-17 17:41:28 Age [y:d:h:m:s]: 01:325:06:36:47
Block: 915245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491312 RingCT/type: yes/0
Extra: 0173c78a7a0bea5e0ee246addd49afd4d766115b375d06dc8ed8ebd0fa3427a49c02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7afc5f04db7cacb15362019fffd4ef3a722e6ca457396c10dcd4012dcde7383 0.600000000000 1372635 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": 915255, "vin": [ { "gen": { "height": 915245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7afc5f04db7cacb15362019fffd4ef3a722e6ca457396c10dcd4012dcde7383" } } ], "extra": [ 1, 115, 199, 138, 122, 11, 234, 94, 14, 226, 70, 173, 221, 73, 175, 212, 215, 102, 17, 91, 55, 93, 6, 220, 142, 216, 235, 208, 250, 52, 39, 164, 156, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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