Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f65134c6a428f920bf75a36f31f64014dc929377039c6b5761d982b6b87d390

Tx prefix hash: 2ad603fb8eea75e825c2401cc23d1c919400775584a5954f0324d7226f89de55
Tx public key: fac2b7dc2d1ef0b1d96109ab1ff7b659e427d52c723f3d04da63263635c9b6b0
Timestamp: 1672603828 Timestamp [UCT]: 2023-01-01 20:10:28 Age [y:d:h:m:s]: 02:018:05:29:00
Block: 665480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534913 RingCT/type: yes/0
Extra: 01fac2b7dc2d1ef0b1d96109ab1ff7b659e427d52c723f3d04da63263635c9b6b002110000000152542ceb000000000000000000

1 output(s) for total of 3.828145799000 dcy

stealth address amount amount idx
00: a60390aae4625f061e4ba18c259d4459ad4bb06bb5132a997a6b6531375d4038 3.828145799000 1106525 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": 665490, "vin": [ { "gen": { "height": 665480 } } ], "vout": [ { "amount": 3828145799, "target": { "key": "a60390aae4625f061e4ba18c259d4459ad4bb06bb5132a997a6b6531375d4038" } } ], "extra": [ 1, 250, 194, 183, 220, 45, 30, 240, 177, 217, 97, 9, 171, 31, 247, 182, 89, 228, 39, 213, 44, 114, 63, 61, 4, 218, 99, 38, 54, 53, 201, 182, 176, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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