Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48d1bec4e8092cad2609418614b2ca96d3e695d8e2d673255123bfb129eb5b78

Tx prefix hash: 761fd59ca3a5f4b5e79c31108c1d2da986797840b661a7d13807457b0b9574d7
Tx public key: 69e0d3e8759b540224fde165f0d8a8aac830804f875429e132ca864649d1bddf
Timestamp: 1707972936 Timestamp [UCT]: 2024-02-15 04:55:36 Age [y:d:h:m:s]: 01:055:22:50:10
Block: 957836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301036 RingCT/type: yes/0
Extra: 0169e0d3e8759b540224fde165f0d8a8aac830804f875429e132ca864649d1bddf0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdf74a59bf4a38f2f86f388fae66faaefb6683a2abf975f447d4898bd2ef3c99 0.600000000000 1417187 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": 957846, "vin": [ { "gen": { "height": 957836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdf74a59bf4a38f2f86f388fae66faaefb6683a2abf975f447d4898bd2ef3c99" } } ], "extra": [ 1, 105, 224, 211, 232, 117, 155, 84, 2, 36, 253, 225, 101, 240, 216, 168, 170, 200, 48, 128, 79, 135, 84, 41, 225, 50, 202, 134, 70, 73, 209, 189, 223, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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