Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4b84a88fa8a5f85f7ad719714a949776227d532f2b15ac304aaddeb77af11c

Tx prefix hash: 4f82aa0e227de36dde99a4de3acb810be25c5de23042ca84fdecb40bfe5df3e8
Tx public key: a30b763e07137ea629ba52cc1f3ab6c1aacf4f1949bd65f540124bd205f6c75e
Timestamp: 1689957497 Timestamp [UCT]: 2023-07-21 16:38:17 Age [y:d:h:m:s]: 01:259:10:15:26
Block: 808750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446513 RingCT/type: yes/0
Extra: 01a30b763e07137ea629ba52cc1f3ab6c1aacf4f1949bd65f540124bd205f6c75e02110000000c75e3f0e9000000000000000000

1 output(s) for total of 1.283144713000 dcy

stealth address amount amount idx
00: 8fe33742050253d155d062268ce87c8bf508b66e522b9f5b320daf0896174c0d 1.283144713000 1260343 of 0

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": 808760, "vin": [ { "gen": { "height": 808750 } } ], "vout": [ { "amount": 1283144713, "target": { "key": "8fe33742050253d155d062268ce87c8bf508b66e522b9f5b320daf0896174c0d" } } ], "extra": [ 1, 163, 11, 118, 62, 7, 19, 126, 166, 41, 186, 82, 204, 31, 58, 182, 193, 170, 207, 79, 25, 73, 189, 101, 245, 64, 18, 75, 210, 5, 246, 199, 94, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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