Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f0450841a5ad023ceb8991ba01308c1d4fd01fe4c375e77c8156fb81571dab

Tx prefix hash: 27e1bb7f8917fccdc2018470fbc97dcf06a687af88ac951e51c20e1f0a80950b
Tx public key: 9e0754e8a6a7a2a885c3b0b2c69f76b8f2b08dd5a7e9adb93fa0c087ef416130
Timestamp: 1646762790 Timestamp [UCT]: 2022-03-08 18:06:30 Age [y:d:h:m:s]: 03:241:06:32:41
Block: 454137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 950289 RingCT/type: yes/0
Extra: 019e0754e8a6a7a2a885c3b0b2c69f76b8f2b08dd5a7e9adb93fa0c087ef41613002110000000e5eb576c5000000000000000000

1 output(s) for total of 19.197994834000 dcy

stealth address amount amount idx
00: 37067ddc6b1209010dda5c6c82db4b9c1e1e16260f1549915f3274a4ddf7a82d 19.197994834000 869730 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": 454147, "vin": [ { "gen": { "height": 454137 } } ], "vout": [ { "amount": 19197994834, "target": { "key": "37067ddc6b1209010dda5c6c82db4b9c1e1e16260f1549915f3274a4ddf7a82d" } } ], "extra": [ 1, 158, 7, 84, 232, 166, 167, 162, 168, 133, 195, 176, 178, 198, 159, 118, 184, 242, 176, 141, 213, 167, 233, 173, 185, 63, 160, 192, 135, 239, 65, 97, 48, 2, 17, 0, 0, 0, 14, 94, 181, 118, 197, 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