Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51036570c6967929478efe5c4361128e7c7ddef210b2e6cad9d72f3327cb3656

Tx prefix hash: 64130d75fd8d45b810f9e6ea24527598bf7ac7d0c2f056c7fea6bfbd7c78736d
Tx public key: e2a6f9a1acc0b3c35a2dcc3ded9bfbc2e4ac79c81b170756902029b39866fb8a
Timestamp: 1713072251 Timestamp [UCT]: 2024-04-14 05:24:11 Age [y:d:h:m:s]: 00:352:04:23:29
Block: 1000103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251784 RingCT/type: yes/0
Extra: 01e2a6f9a1acc0b3c35a2dcc3ded9bfbc2e4ac79c81b170756902029b39866fb8a021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd871121e9ffa7fb796cd6eb9ed70c4dd2e8e3b6ccd09f4f18c816c7156bf082 0.600000000000 1460593 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": 1000113, "vin": [ { "gen": { "height": 1000103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd871121e9ffa7fb796cd6eb9ed70c4dd2e8e3b6ccd09f4f18c816c7156bf082" } } ], "extra": [ 1, 226, 166, 249, 161, 172, 192, 179, 195, 90, 45, 204, 61, 237, 155, 251, 194, 228, 172, 121, 200, 27, 23, 7, 86, 144, 32, 41, 179, 152, 102, 251, 138, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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