Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e1d97269f983472f8314384e4074615801f1326adc7a9dfd100689b9b2acef

Tx prefix hash: 8c9c49a60979b601cd85eccba3fe93ecb49b3e6cc52c587646685f216b16736b
Tx public key: f378435d59d8fd28117ed56b1a687e87dc7ab7457d77641067ede70c1447ff61
Timestamp: 1579009428 Timestamp [UCT]: 2020-01-14 13:43:48 Age [y:d:h:m:s]: 05:092:13:54:45
Block: 45304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1216427 RingCT/type: yes/0
Extra: 01f378435d59d8fd28117ed56b1a687e87dc7ab7457d77641067ede70c1447ff61021100000018dcee4b4d000000000000000000

1 output(s) for total of 434.400064712000 dcy

stealth address amount amount idx
00: 812ef070730fd7fdee08a9d99fbc100adae48c9ce5c879f7d646f1519f3c4dc2 434.400064712000 82729 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": 45314, "vin": [ { "gen": { "height": 45304 } } ], "vout": [ { "amount": 434400064712, "target": { "key": "812ef070730fd7fdee08a9d99fbc100adae48c9ce5c879f7d646f1519f3c4dc2" } } ], "extra": [ 1, 243, 120, 67, 93, 89, 216, 253, 40, 17, 126, 213, 107, 26, 104, 126, 135, 220, 122, 183, 69, 125, 119, 100, 16, 103, 237, 231, 12, 20, 71, 255, 97, 2, 17, 0, 0, 0, 24, 220, 238, 75, 77, 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