Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99760f692bf3815d6669beb72c20ebc660aba83cd1ac43d9506a7780b432f212

Tx prefix hash: 8ed7ae5e883aa2dbac5bbbd703263a11800553e71e8533af89a32e89f6709b6e
Tx public key: f23e21d85f4e371cccf3ff86da14b1f96e678a97ce16e41bfc1f7bbbc48aa2a8
Timestamp: 1708836479 Timestamp [UCT]: 2024-02-25 04:47:59 Age [y:d:h:m:s]: 01:257:19:06:41
Block: 965011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442977 RingCT/type: yes/0
Extra: 01f23e21d85f4e371cccf3ff86da14b1f96e678a97ce16e41bfc1f7bbbc48aa2a80211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24c2f907191859f0b585cd5fbf99526797fb15ee9821dc0e8e673b7bc36cd915 0.600000000000 1424758 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": 965021, "vin": [ { "gen": { "height": 965011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24c2f907191859f0b585cd5fbf99526797fb15ee9821dc0e8e673b7bc36cd915" } } ], "extra": [ 1, 242, 62, 33, 216, 95, 78, 55, 28, 204, 243, 255, 134, 218, 20, 177, 249, 110, 103, 138, 151, 206, 22, 228, 27, 252, 31, 123, 187, 196, 138, 162, 168, 2, 17, 0, 0, 0, 5, 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