Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac001edc169f524bd443668d70cf1fc7a51024624dab8d561e86424357d8131c

Tx prefix hash: 628a48c6dacd95725b6e97f0975d7d61fe0a48b5bfe63dea238a7c4c2c45b237
Tx public key: a9a7c09d1f047cc86797d7a6b1e8ec83c40f58a785451050a930fc60ea1ffb12
Timestamp: 1730978731 Timestamp [UCT]: 2024-11-07 11:25:31 Age [y:d:h:m:s]: 00:162:03:17:07
Block: 1148488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115721 RingCT/type: yes/0
Extra: 01a9a7c09d1f047cc86797d7a6b1e8ec83c40f58a785451050a930fc60ea1ffb120211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a08498b0f5adbff70e89a2e2db742305177befc5b473413845ae365fe91e9536 0.600000000000 1633347 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": 1148498, "vin": [ { "gen": { "height": 1148488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a08498b0f5adbff70e89a2e2db742305177befc5b473413845ae365fe91e9536" } } ], "extra": [ 1, 169, 167, 192, 157, 31, 4, 124, 200, 103, 151, 215, 166, 177, 232, 236, 131, 196, 15, 88, 167, 133, 69, 16, 80, 169, 48, 252, 96, 234, 31, 251, 18, 2, 17, 0, 0, 0, 7, 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