Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cd2af759742784fea908c26d6ec129dae1fbff1c4278f3867796dc4d7e047c2

Tx prefix hash: 2b89e33ead53f020c76f1edaf985af12431efa357f973f7b0b402b4cc3573053
Tx public key: 7c5e983705503b1457855ce9c3818b5fe97f8235dfdd9d9673843274706c471b
Timestamp: 1582254842 Timestamp [UCT]: 2020-02-21 03:14:02 Age [y:d:h:m:s]: 05:024:04:46:46
Block: 69288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170424 RingCT/type: yes/0
Extra: 017c5e983705503b1457855ce9c3818b5fe97f8235dfdd9d9673843274706c471b02110000000103d36d11000000000000000000

1 output(s) for total of 361.760293964000 dcy

stealth address amount amount idx
00: 779b4e17fdc7c89fdc4602a52344aac410c8efa70a3f8a5f571fedf945c76fe8 361.760293964000 127746 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": 69298, "vin": [ { "gen": { "height": 69288 } } ], "vout": [ { "amount": 361760293964, "target": { "key": "779b4e17fdc7c89fdc4602a52344aac410c8efa70a3f8a5f571fedf945c76fe8" } } ], "extra": [ 1, 124, 94, 152, 55, 5, 80, 59, 20, 87, 133, 92, 233, 195, 129, 139, 95, 233, 127, 130, 53, 223, 221, 157, 150, 115, 132, 50, 116, 112, 108, 71, 27, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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