Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a00d77fb1ede4fde4923585214f7b582d3c0e192724a4e61cf76952c53fe0b29

Tx prefix hash: 4ee67b3f1ab052f35353003963e8fd79363388cc053b1bc67d79b895ecaa22c2
Tx public key: facb270df89f61b9dc2b0d514bec52bece2db297673720e96c576bd95528f236
Timestamp: 1728746526 Timestamp [UCT]: 2024-10-12 15:22:06 Age [y:d:h:m:s]: 01:039:10:10:16
Block: 1130063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286553 RingCT/type: yes/0
Extra: 01facb270df89f61b9dc2b0d514bec52bece2db297673720e96c576bd95528f23602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffdaf2453b7cea73aac9a5e49491d4ce5fc3fb1b9b5e15e22827eb9fd2cb41ee 0.600000000000 1612934 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": 1130073, "vin": [ { "gen": { "height": 1130063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffdaf2453b7cea73aac9a5e49491d4ce5fc3fb1b9b5e15e22827eb9fd2cb41ee" } } ], "extra": [ 1, 250, 203, 39, 13, 248, 159, 97, 185, 220, 43, 13, 81, 75, 236, 82, 190, 206, 45, 178, 151, 103, 55, 32, 233, 108, 87, 107, 217, 85, 40, 242, 54, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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