Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54c1faae85a9711570091e162688688a1322aafcd6a058c0a1da79bda9299d0c

Tx prefix hash: 140c73788c297df0502ace22e822d0f1d8cc73b094e7ce6ddfd753b2307e6644
Tx public key: 9555fd050d80a99fe1b741db3e49cfecf2ca0e0a6f22f28ba4f7de4026b8d532
Timestamp: 1735514763 Timestamp [UCT]: 2024-12-29 23:26:03 Age [y:d:h:m:s]: 00:169:17:03:00
Block: 1186040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121024 RingCT/type: yes/0
Extra: 019555fd050d80a99fe1b741db3e49cfecf2ca0e0a6f22f28ba4f7de4026b8d53202110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7820aaa2265750880a49feee3c1cfdc26d066372f44aeb5440ab6ac0adf537e3 0.600000000000 1672515 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": 1186050, "vin": [ { "gen": { "height": 1186040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7820aaa2265750880a49feee3c1cfdc26d066372f44aeb5440ab6ac0adf537e3" } } ], "extra": [ 1, 149, 85, 253, 5, 13, 128, 169, 159, 225, 183, 65, 219, 62, 73, 207, 236, 242, 202, 14, 10, 111, 34, 242, 139, 164, 247, 222, 64, 38, 184, 213, 50, 2, 17, 0, 0, 0, 10, 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