Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68e363ee953fd09d77d9d0bbcd36b21d0f683c0d3565ad9b9480f5fb5090b8c5

Tx prefix hash: 61c44f80e90168cefaa8b862825b95b3fcb58e62ddae4991c5062f1cce1d2de6
Tx public key: f0cf9b91cfaae8d99a4d3f432b4730390d73e3f19ac9565cef0be9e137ac00c6
Timestamp: 1580974359 Timestamp [UCT]: 2020-02-06 07:32:39 Age [y:d:h:m:s]: 04:239:02:59:36
Block: 59515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1062531 RingCT/type: yes/0
Extra: 01f0cf9b91cfaae8d99a4d3f432b4730390d73e3f19ac9565cef0be9e137ac00c6021100000003724f989b000000000000000000

1 output(s) for total of 389.765072069000 dcy

stealth address amount amount idx
00: 6f21bc1d950441bec5696f7d03be6d0c1e0ced5209552e7bfe5e60dfccb5a664 389.765072069000 109923 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": 59525, "vin": [ { "gen": { "height": 59515 } } ], "vout": [ { "amount": 389765072069, "target": { "key": "6f21bc1d950441bec5696f7d03be6d0c1e0ced5209552e7bfe5e60dfccb5a664" } } ], "extra": [ 1, 240, 207, 155, 145, 207, 170, 232, 217, 154, 77, 63, 67, 43, 71, 48, 57, 13, 115, 227, 241, 154, 201, 86, 92, 239, 11, 233, 225, 55, 172, 0, 198, 2, 17, 0, 0, 0, 3, 114, 79, 152, 155, 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