Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89184d459bf5dd365f5a8f6088f8738ba323f9147522bdd72c12aed629b958e9

Tx prefix hash: b715d42f124d3d0a91624fb0b576f0d2bd8f4e9f271abe475ae8be45c1d5f897
Tx public key: 98900bce0f89ad218e0814f2ff196b643716b32fd9223f28df1f27cd875f9edd
Timestamp: 1707941537 Timestamp [UCT]: 2024-02-14 20:12:17 Age [y:d:h:m:s]: 01:291:22:24:55
Block: 957574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467442 RingCT/type: yes/0
Extra: 0198900bce0f89ad218e0814f2ff196b643716b32fd9223f28df1f27cd875f9edd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5df0cacb7280211db4aed8d81bc3f8553920c35d2d61574c53f20db89632a0b1 0.600000000000 1416892 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": 957584, "vin": [ { "gen": { "height": 957574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5df0cacb7280211db4aed8d81bc3f8553920c35d2d61574c53f20db89632a0b1" } } ], "extra": [ 1, 152, 144, 11, 206, 15, 137, 173, 33, 142, 8, 20, 242, 255, 25, 107, 100, 55, 22, 179, 47, 217, 34, 63, 40, 223, 31, 39, 205, 135, 95, 158, 221, 2, 17, 0, 0, 0, 1, 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