Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d0bdb7b4639a80bd174e2bb9631e6cf542a46553cf370ae886b7e5411c8a632

Tx prefix hash: 6bb3f00dc68e1bba3e64ee6c1871acdc1f653f5534812dfa409ed31712f0087c
Tx public key: d71cc3975fe8e5f666e40e76c0d20dbaf2114bdd0a6c7b4ab1697f0edc985c4d
Timestamp: 1724216377 Timestamp [UCT]: 2024-08-21 04:59:37 Age [y:d:h:m:s]: 00:159:14:21:53
Block: 1092519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113912 RingCT/type: yes/0
Extra: 01d71cc3975fe8e5f666e40e76c0d20dbaf2114bdd0a6c7b4ab1697f0edc985c4d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e68ee6ed05eeb53935d4491bc55cdce3025a84f9956acccc953eb59e7d8986b 0.600000000000 1567282 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": 1092529, "vin": [ { "gen": { "height": 1092519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e68ee6ed05eeb53935d4491bc55cdce3025a84f9956acccc953eb59e7d8986b" } } ], "extra": [ 1, 215, 28, 195, 151, 95, 232, 229, 246, 102, 228, 14, 118, 192, 210, 13, 186, 242, 17, 75, 221, 10, 108, 123, 74, 177, 105, 127, 14, 220, 152, 92, 77, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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