Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf9b25ed25ad8e44d3c31197caf37c71ebc29f19422161ef62b5c87a66960ee4

Tx prefix hash: 2742b081d7fdfdf3586163cff4e2a7f30d7e5a472d508c4444281f910322f25a
Tx public key: c29c673edd3defe99d0008b23cde9023b155c10f89e694ae3d8f8e4a6b58c405
Timestamp: 1699815154 Timestamp [UCT]: 2023-11-12 18:52:34 Age [y:d:h:m:s]: 01:182:01:47:13
Block: 890217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391330 RingCT/type: yes/0
Extra: 01c29c673edd3defe99d0008b23cde9023b155c10f89e694ae3d8f8e4a6b58c40502110000000133af99f4000000000000000000

1 output(s) for total of 0.689194067000 dcy

stealth address amount amount idx
00: b088e14abe9a8c027e2e7a6f70c4e8494eddc93a84f0a93c96313cf0212c36c6 0.689194067000 1346240 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": 890227, "vin": [ { "gen": { "height": 890217 } } ], "vout": [ { "amount": 689194067, "target": { "key": "b088e14abe9a8c027e2e7a6f70c4e8494eddc93a84f0a93c96313cf0212c36c6" } } ], "extra": [ 1, 194, 156, 103, 62, 221, 61, 239, 233, 157, 0, 8, 178, 60, 222, 144, 35, 177, 85, 193, 15, 137, 230, 148, 174, 61, 143, 142, 74, 107, 88, 196, 5, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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