Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8eda99366525f1c8d7ddf63f09c6e1ce0e58b665dc359a28a8faa5a3cd480d0

Tx prefix hash: 484d870574703befd0b4dff5f244f10292098a9d0d1cd9e79d884f9b86e1deb1
Tx public key: ba933d4a636cf75742bdd588688cae88ef1c49e91fc3e4048e65042fbe3454ef
Timestamp: 1698798941 Timestamp [UCT]: 2023-11-01 00:35:41 Age [y:d:h:m:s]: 01:230:15:40:43
Block: 881996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425769 RingCT/type: yes/0
Extra: 01ba933d4a636cf75742bdd588688cae88ef1c49e91fc3e4048e65042fbe3454ef02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.733805779000 dcy

stealth address amount amount idx
00: ad27a1d168e798d74e37ae3db32ed8dc93b3c831cf48def67a592990b0a173f4 0.733805779000 1337626 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": 882006, "vin": [ { "gen": { "height": 881996 } } ], "vout": [ { "amount": 733805779, "target": { "key": "ad27a1d168e798d74e37ae3db32ed8dc93b3c831cf48def67a592990b0a173f4" } } ], "extra": [ 1, 186, 147, 61, 74, 99, 108, 247, 87, 66, 189, 213, 136, 104, 140, 174, 136, 239, 28, 73, 233, 31, 195, 228, 4, 142, 101, 4, 47, 190, 52, 84, 239, 2, 17, 0, 0, 0, 13, 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