Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea527fa48eefe5afd872ecb3ad1788e9b26491a9a86c88fa7505b4f97c42f0a

Tx prefix hash: fb358668cef25b3c1b8c79cc501471ea744955f6dbbc1c635d1ec52cd5c7afa3
Tx public key: 6f02f4d9c3acb34b498cb10ec6bcabb82487c5b324b61fbfabfebaf554a9143b
Timestamp: 1732783092 Timestamp [UCT]: 2024-11-28 08:38:12 Age [y:d:h:m:s]: 00:114:18:27:05
Block: 1163433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81836 RingCT/type: yes/0
Extra: 016f02f4d9c3acb34b498cb10ec6bcabb82487c5b324b61fbfabfebaf554a9143b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34227da6731772a8858dc1a164be5625751ab3db0206e8be173df0f2a2ab4ad4 0.600000000000 1649100 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": 1163443, "vin": [ { "gen": { "height": 1163433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34227da6731772a8858dc1a164be5625751ab3db0206e8be173df0f2a2ab4ad4" } } ], "extra": [ 1, 111, 2, 244, 217, 195, 172, 179, 75, 73, 140, 177, 14, 198, 188, 171, 184, 36, 135, 197, 179, 36, 182, 31, 191, 171, 254, 186, 245, 84, 169, 20, 59, 2, 17, 0, 0, 0, 3, 31, 10, 83, 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