Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f182d26f085bdfce9cf7391413dd8897b870b1ffd916bdf98aeec1371ec62cd

Tx prefix hash: 1e0c74f3d2963565a5c8b287c18de86065bc561948b4dff63e85a051ed6e4dec
Tx public key: 2fb1d7a7066e34ee73f92a762f38c66a176837e06b3dd972614083a2e8f046d9
Timestamp: 1705007906 Timestamp [UCT]: 2024-01-11 21:18:26 Age [y:d:h:m:s]: 01:140:11:21:11
Block: 933241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361552 RingCT/type: yes/0
Extra: 012fb1d7a7066e34ee73f92a762f38c66a176837e06b3dd972614083a2e8f046d90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa9c3794ca4f709281e9ea9880b9bf1cbaed61da0212278db4b1a00dde39af7 0.600000000000 1391201 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": 933251, "vin": [ { "gen": { "height": 933241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa9c3794ca4f709281e9ea9880b9bf1cbaed61da0212278db4b1a00dde39af7" } } ], "extra": [ 1, 47, 177, 215, 167, 6, 110, 52, 238, 115, 249, 42, 118, 47, 56, 198, 106, 23, 104, 55, 224, 107, 61, 217, 114, 97, 64, 131, 162, 232, 240, 70, 217, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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