Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12b24d33f0fe0315148b5e70300dd138ee242288bdf98b122ea26b4d4177daee

Tx prefix hash: 15162c678490338a1d9def3ab6d44b54fdd45bd74a09c2403e58c9e96cbcfb71
Tx public key: 032e2c5c5776b08c6a3e344ac9a74b282c42273faef056b09d5adce749f3773a
Timestamp: 1582382007 Timestamp [UCT]: 2020-02-22 14:33:27 Age [y:d:h:m:s]: 04:307:22:18:10
Block: 70217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112669 RingCT/type: yes/0
Extra: 01032e2c5c5776b08c6a3e344ac9a74b282c42273faef056b09d5adce749f3773a021100000001c71d3ff9000000000000000000

1 output(s) for total of 359.205298288000 dcy

stealth address amount amount idx
00: 43a5f24468a7442c465394e0d43b4ea8e4c5ee2bfb10f9f729df4e2f243faeb7 359.205298288000 129668 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": 70227, "vin": [ { "gen": { "height": 70217 } } ], "vout": [ { "amount": 359205298288, "target": { "key": "43a5f24468a7442c465394e0d43b4ea8e4c5ee2bfb10f9f729df4e2f243faeb7" } } ], "extra": [ 1, 3, 46, 44, 92, 87, 118, 176, 140, 106, 62, 52, 74, 201, 167, 75, 40, 44, 66, 39, 63, 174, 240, 86, 176, 157, 90, 220, 231, 73, 243, 119, 58, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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