Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c18b4aa37e94928c0022fd3a467515500356a9603b6dfa993e842ed674fc2b

Tx prefix hash: 2f28805b46981cea2ff3fec1c06a09fc71f24467b752a1bcf5ec1a6a241b9cd8
Tx public key: bef72c927cb7c09cc352a4f3645959bb21470b2309a8f10d623eb21b2a1bb36c
Timestamp: 1736916106 Timestamp [UCT]: 2025-01-15 04:41:46 Age [y:d:h:m:s]: 00:154:09:39:23
Block: 1197648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110051 RingCT/type: yes/0
Extra: 01bef72c927cb7c09cc352a4f3645959bb21470b2309a8f10d623eb21b2a1bb36c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fede1c3240eee12fb3883a87905b534d069500caa28e9ed8815a5d41977d7733 0.600000000000 1684261 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": 1197658, "vin": [ { "gen": { "height": 1197648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fede1c3240eee12fb3883a87905b534d069500caa28e9ed8815a5d41977d7733" } } ], "extra": [ 1, 190, 247, 44, 146, 124, 183, 192, 156, 195, 82, 164, 243, 100, 89, 89, 187, 33, 71, 11, 35, 9, 168, 241, 13, 98, 62, 178, 27, 42, 27, 179, 108, 2, 17, 0, 0, 0, 2, 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