Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7479fa5f7bc32d6a5a6819e4b80d6f2735f80edc4a46fd7aa82e8d157c8f95af

Tx prefix hash: d9347c959cec7b46119d8e80fbe0b9c444609a82544b9b463dc4143879f6c5fe
Tx public key: 792100420c0ef0f62b64479cb3fb5a22295131c9f80d844211ba1542356bde66
Timestamp: 1693807588 Timestamp [UCT]: 2023-09-04 06:06:28 Age [y:d:h:m:s]: 01:136:13:21:59
Block: 840590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358938 RingCT/type: yes/0
Extra: 01792100420c0ef0f62b64479cb3fb5a22295131c9f80d844211ba1542356bde6602110000000f33af99f4000000000000000000

1 output(s) for total of 1.006413503000 dcy

stealth address amount amount idx
00: 27fc4c6c77e991ae07e11045f961da7bebd1e571e4f0878bc799b1204ff35a39 1.006413503000 1293540 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": 840600, "vin": [ { "gen": { "height": 840590 } } ], "vout": [ { "amount": 1006413503, "target": { "key": "27fc4c6c77e991ae07e11045f961da7bebd1e571e4f0878bc799b1204ff35a39" } } ], "extra": [ 1, 121, 33, 0, 66, 12, 14, 240, 246, 43, 100, 71, 156, 179, 251, 90, 34, 41, 81, 49, 201, 248, 13, 132, 66, 17, 186, 21, 66, 53, 107, 222, 102, 2, 17, 0, 0, 0, 15, 51, 175, 153, 244, 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