Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5edba4ca73ebd64305da070d66abb0d883fc4b7306c20ce6cf13463cbc611a0

Tx prefix hash: 60c0333ba36b7c1beaaa197c316f4c03dccdc0dd26764707c668496d9b36af21
Tx public key: b0e554c20d94577d20beb902b7ff0fea77f24cb0d692d23846f863fd8a5b2c16
Timestamp: 1643503536 Timestamp [UCT]: 2022-01-30 00:45:36 Age [y:d:h:m:s]: 03:279:13:58:23
Block: 428135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 976720 RingCT/type: yes/0
Extra: 01b0e554c20d94577d20beb902b7ff0fea77f24cb0d692d23846f863fd8a5b2c16021100000003d3fcec30000000000000000000

1 output(s) for total of 23.410534449000 dcy

stealth address amount amount idx
00: 5fb9acf5f6e8c9a37efa2d0689d30bdf057f1f49880ff68c853623a20a3bf556 23.410534449000 837455 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": 428145, "vin": [ { "gen": { "height": 428135 } } ], "vout": [ { "amount": 23410534449, "target": { "key": "5fb9acf5f6e8c9a37efa2d0689d30bdf057f1f49880ff68c853623a20a3bf556" } } ], "extra": [ 1, 176, 229, 84, 194, 13, 148, 87, 125, 32, 190, 185, 2, 183, 255, 15, 234, 119, 242, 76, 176, 214, 146, 210, 56, 70, 248, 99, 253, 138, 91, 44, 22, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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