Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 508e65110acc1c3ef76c5f2a8ecc6dcd5e144e32faa837c02dc74fef4e10932f

Tx prefix hash: 472deeafd4ce647d8a6a63bee0767e40c0c655d2baaada6125d5d1384566fa15
Tx public key: db81fe3bef220423e31c390f4934f65c87fe3e4e62f8f84471b212fb6541fa22
Timestamp: 1728298749 Timestamp [UCT]: 2024-10-07 10:59:09 Age [y:d:h:m:s]: 00:178:14:02:49
Block: 1126354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127430 RingCT/type: yes/0
Extra: 01db81fe3bef220423e31c390f4934f65c87fe3e4e62f8f84471b212fb6541fa2202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa0278c03638b12971a76cc16e6a0c5dac65a0ff66faeaa0ca4883ab5b681ccd 0.600000000000 1609145 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": 1126364, "vin": [ { "gen": { "height": 1126354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa0278c03638b12971a76cc16e6a0c5dac65a0ff66faeaa0ca4883ab5b681ccd" } } ], "extra": [ 1, 219, 129, 254, 59, 239, 34, 4, 35, 227, 28, 57, 15, 73, 52, 246, 92, 135, 254, 62, 78, 98, 248, 248, 68, 113, 178, 18, 251, 101, 65, 250, 34, 2, 17, 0, 0, 0, 2, 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