Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9af9cffd918b84c96fcb8eb9ebb76ecee91c91021838b1530c6add4be6ca9d0

Tx prefix hash: 61061b90decb9df4a2079e8c1f8d5e8c80c1bdc1ef7e97144822ea05a1ca0aa9
Tx public key: 78435715644b27d81b0b30ccfb635bfff6b81af73ceebbb434459477e1a624ed
Timestamp: 1719063599 Timestamp [UCT]: 2024-06-22 13:39:59 Age [y:d:h:m:s]: 00:289:18:28:21
Block: 1049777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207072 RingCT/type: yes/0
Extra: 0178435715644b27d81b0b30ccfb635bfff6b81af73ceebbb434459477e1a624ed02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91e4600761845de7c94f33680b91d3a9e41219dc6e896d2eb04e90e3de9c4418 0.600000000000 1519882 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": 1049787, "vin": [ { "gen": { "height": 1049777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91e4600761845de7c94f33680b91d3a9e41219dc6e896d2eb04e90e3de9c4418" } } ], "extra": [ 1, 120, 67, 87, 21, 100, 75, 39, 216, 27, 11, 48, 204, 251, 99, 91, 255, 246, 184, 26, 247, 60, 238, 187, 180, 52, 69, 148, 119, 225, 166, 36, 237, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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