Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a0f2d68af4163308c5cf14d86da1e0d224dcef5d36608965f117a6185826486

Tx prefix hash: c521cdb0f99dd038955ea370aa023f6adb29b8fc3ab637934de705a3beb59246
Tx public key: 0634c0e851ff5f7e385b6c385e58be9aa8acf43b90007e977ba862aed3a060a9
Timestamp: 1715527585 Timestamp [UCT]: 2024-05-12 15:26:25 Age [y:d:h:m:s]: 01:038:05:21:42
Block: 1020515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288081 RingCT/type: yes/0
Extra: 010634c0e851ff5f7e385b6c385e58be9aa8acf43b90007e977ba862aed3a060a9021100000005679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdd86eeb233d696eb009f0a65c4447876c6cc0ce786f79769b7cde1f6c03c188 0.600000000000 1484592 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": 1020525, "vin": [ { "gen": { "height": 1020515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdd86eeb233d696eb009f0a65c4447876c6cc0ce786f79769b7cde1f6c03c188" } } ], "extra": [ 1, 6, 52, 192, 232, 81, 255, 95, 126, 56, 91, 108, 56, 94, 88, 190, 154, 168, 172, 244, 59, 144, 0, 126, 151, 123, 168, 98, 174, 211, 160, 96, 169, 2, 17, 0, 0, 0, 5, 103, 154, 138, 129, 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