Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 693d151f09d30e52e30c6f9974f8b45529a07dd4a4681766f3e59c1444c95f4b

Tx prefix hash: 0193e42f6ee13dc1a1237cb1b5881e5209de90a488f40978785aaf37a2723ba4
Tx public key: 6a6ba7d139101d066167ec8a4857c925082e3d5d0e9a49c6647053ce64cbd670
Timestamp: 1723019264 Timestamp [UCT]: 2024-08-07 08:27:44 Age [y:d:h:m:s]: 00:243:08:31:04
Block: 1082584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173805 RingCT/type: yes/0
Extra: 016a6ba7d139101d066167ec8a4857c925082e3d5d0e9a49c6647053ce64cbd67002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95adc5f4cea3efed129f2b0e7e23faa286492c6da8975af3b1bc6926b7c41dc1 0.600000000000 1556413 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": 1082594, "vin": [ { "gen": { "height": 1082584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95adc5f4cea3efed129f2b0e7e23faa286492c6da8975af3b1bc6926b7c41dc1" } } ], "extra": [ 1, 106, 107, 167, 209, 57, 16, 29, 6, 97, 103, 236, 138, 72, 87, 201, 37, 8, 46, 61, 93, 14, 154, 73, 198, 100, 112, 83, 206, 100, 203, 214, 112, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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