Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 700bad7008123bb7e0051e63b3c9c7fb77918fe4c310d0d6bac9dec2ead0e98d

Tx prefix hash: 2315f026bb5d1e0ca44a9838da90a77f83d66a3b0f90df47b77646a74be0fd0c
Tx public key: c0c354447ab48eabc977d190db2a384a1e19e872257cfb5ed682f6b8669aff49
Timestamp: 1706746049 Timestamp [UCT]: 2024-02-01 00:07:29 Age [y:d:h:m:s]: 01:025:07:32:03
Block: 947650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279131 RingCT/type: yes/0
Extra: 01c0c354447ab48eabc977d190db2a384a1e19e872257cfb5ed682f6b8669aff490211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c245f1a843606b715faa5c1b0ec2849eea9001bf888f60b4e10339e3d3b55b7c 0.600000000000 1406008 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": 947660, "vin": [ { "gen": { "height": 947650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c245f1a843606b715faa5c1b0ec2849eea9001bf888f60b4e10339e3d3b55b7c" } } ], "extra": [ 1, 192, 195, 84, 68, 122, 180, 142, 171, 201, 119, 209, 144, 219, 42, 56, 74, 30, 25, 232, 114, 37, 124, 251, 94, 214, 130, 246, 184, 102, 154, 255, 73, 2, 17, 0, 0, 0, 4, 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