Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e83400f1027c0418f32e9d2edc62b681b1ef5eb65c5c36ea124a77b643046482

Tx prefix hash: 0c57b50aa6c33c7bb3dcf0640b32cf4645e89ad063a9a04a0adc4f5a4de3cdd1
Tx public key: 3e373e78ca4f2b77bfd8f1c898d19cf6168ba5bee4a1bfd5a438d6a79ed7a6e5
Timestamp: 1715109127 Timestamp [UCT]: 2024-05-07 19:12:07 Age [y:d:h:m:s]: 00:191:04:34:12
Block: 1017012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136858 RingCT/type: yes/0
Extra: 013e373e78ca4f2b77bfd8f1c898d19cf6168ba5bee4a1bfd5a438d6a79ed7a6e50211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96de17669ff129191eeb13b738b7bf123f880936adcdd56faa3b6f838e6e30e7 0.600000000000 1480761 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": 1017022, "vin": [ { "gen": { "height": 1017012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96de17669ff129191eeb13b738b7bf123f880936adcdd56faa3b6f838e6e30e7" } } ], "extra": [ 1, 62, 55, 62, 120, 202, 79, 43, 119, 191, 216, 241, 200, 152, 209, 156, 246, 22, 139, 165, 190, 228, 161, 191, 213, 164, 56, 214, 167, 158, 215, 166, 229, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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