Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a0c0671bfd1036d6b0bd1247ad03e43c6670bdbec6f6440034b496344a420e

Tx prefix hash: ea74605571f17ae6d3bc998b0bdc90ea0648cc2197138e266eadd29ac77e4dce
Tx public key: b0c14735f5f77c62e815c322fb785326d5493041acac516d36178548f3fe0a1a
Timestamp: 1736818929 Timestamp [UCT]: 2025-01-14 01:42:09 Age [y:d:h:m:s]: 00:062:10:48:23
Block: 1196847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44422 RingCT/type: yes/0
Extra: 01b0c14735f5f77c62e815c322fb785326d5493041acac516d36178548f3fe0a1a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6ebf58d8d63cc6502f8ea6cc186b973a39cdc9e6684fb7d6ef92dfb23b6d51c 0.600000000000 1683450 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": 1196857, "vin": [ { "gen": { "height": 1196847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6ebf58d8d63cc6502f8ea6cc186b973a39cdc9e6684fb7d6ef92dfb23b6d51c" } } ], "extra": [ 1, 176, 193, 71, 53, 245, 247, 124, 98, 232, 21, 195, 34, 251, 120, 83, 38, 213, 73, 48, 65, 172, 172, 81, 109, 54, 23, 133, 72, 243, 254, 10, 26, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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