Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc470ab0954f3fc510bc1d38cf4be1c4d4ab688c2ec7bb65ea0d128acc681617

Tx prefix hash: 61f6439521d11e1872baac2223c0c34cca6c7f4c3091f270de23eeaa830d6fa2
Tx public key: 8f107990547cad6614b191c69c9bac1dd7c4a1019e8d6dcd62968403c2652879
Timestamp: 1698782383 Timestamp [UCT]: 2023-10-31 19:59:43 Age [y:d:h:m:s]: 01:205:13:54:30
Block: 881862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407960 RingCT/type: yes/0
Extra: 018f107990547cad6614b191c69c9bac1dd7c4a1019e8d6dcd62968403c265287902110000000575e3f0e9000000000000000000

1 output(s) for total of 0.734556364000 dcy

stealth address amount amount idx
00: 8365ff4b1c810e0de9fc20eac4392a77bbe9f4f448a085210c56975f444ef2ac 0.734556364000 1337484 of 0

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": 881872, "vin": [ { "gen": { "height": 881862 } } ], "vout": [ { "amount": 734556364, "target": { "key": "8365ff4b1c810e0de9fc20eac4392a77bbe9f4f448a085210c56975f444ef2ac" } } ], "extra": [ 1, 143, 16, 121, 144, 84, 124, 173, 102, 20, 177, 145, 198, 156, 155, 172, 29, 215, 196, 161, 1, 158, 141, 109, 205, 98, 150, 132, 3, 194, 101, 40, 121, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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