Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856f347d3d6b8dbb78c8b363ea7ba9bcac8acaefa1b400ee11722d3ddf49874e

Tx prefix hash: 3c4ef44e2f8d562ad9425db53e8082e153adca4b97a1e681b7935c3a8c0558ca
Tx public key: 4f42ae1de581fa824d5a587e418475e2937f3f2bcdb2fbf722fcc9e30cd8e0c9
Timestamp: 1702736414 Timestamp [UCT]: 2023-12-16 14:20:14 Age [y:d:h:m:s]: 01:035:02:08:42
Block: 914424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286402 RingCT/type: yes/0
Extra: 014f42ae1de581fa824d5a587e418475e2937f3f2bcdb2fbf722fcc9e30cd8e0c9021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e90c81b18c28ed82fa3f681ee8ff5419704cb64e299572c1d1c8c1976ed91f1 0.600000000000 1371740 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": 914434, "vin": [ { "gen": { "height": 914424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e90c81b18c28ed82fa3f681ee8ff5419704cb64e299572c1d1c8c1976ed91f1" } } ], "extra": [ 1, 79, 66, 174, 29, 229, 129, 250, 130, 77, 90, 88, 126, 65, 132, 117, 226, 147, 127, 63, 43, 205, 178, 251, 247, 34, 252, 201, 227, 12, 216, 224, 201, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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