Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c81a255777bf10399890b001e717009ad3f097bac6225509bd42e3b0fbd36a

Tx prefix hash: 191b855f1bd393d23c11ae728d51430fbda52e51ddd37488bd6e2b45430f1fbc
Tx public key: 5af89add22f39185c1cbbdf70995c0a01732d80bcb8af615de70e7d037e7a490
Timestamp: 1731096664 Timestamp [UCT]: 2024-11-08 20:11:04 Age [y:d:h:m:s]: 00:142:11:10:44
Block: 1149473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101632 RingCT/type: yes/0
Extra: 015af89add22f39185c1cbbdf70995c0a01732d80bcb8af615de70e7d037e7a490021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb664692cc685c92d84b8e918d1c6cb1e93dec6da004d0abac5d43df84726e2c 0.600000000000 1634558 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": 1149483, "vin": [ { "gen": { "height": 1149473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb664692cc685c92d84b8e918d1c6cb1e93dec6da004d0abac5d43df84726e2c" } } ], "extra": [ 1, 90, 248, 154, 221, 34, 243, 145, 133, 193, 203, 189, 247, 9, 149, 192, 160, 23, 50, 216, 11, 203, 138, 246, 21, 222, 112, 231, 208, 55, 231, 164, 144, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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