Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f3166d38e0a8eb79e3cc517319f74294ffee96da09035c1b355c7aa6454597

Tx prefix hash: 871b5426171741c826df599bb392ee13e3258f2c3b8228e9aafe5c516e523e7e
Tx public key: 03025766ba3e36d6d9c1564ea3a28530d7b75d74a09ba6071dd1f39df87fba0f
Timestamp: 1719802618 Timestamp [UCT]: 2024-07-01 02:56:58 Age [y:d:h:m:s]: 00:205:20:22:54
Block: 1055917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147254 RingCT/type: yes/0
Extra: 0103025766ba3e36d6d9c1564ea3a28530d7b75d74a09ba6071dd1f39df87fba0f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f65ee2926c3d0dc8be6ecb97ff1c9868715eb40e4b69c1dd246c5525e62b6a 0.600000000000 1526324 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": 1055927, "vin": [ { "gen": { "height": 1055917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f65ee2926c3d0dc8be6ecb97ff1c9868715eb40e4b69c1dd246c5525e62b6a" } } ], "extra": [ 1, 3, 2, 87, 102, 186, 62, 54, 214, 217, 193, 86, 78, 163, 162, 133, 48, 215, 183, 93, 116, 160, 155, 166, 7, 29, 209, 243, 157, 248, 127, 186, 15, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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