Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8671f48e2c10aa4b391e9a6f9efa8e5ca8068b89edb51acb57d23c2eeab5a6ae

Tx prefix hash: ba6eec015a22af52a77562e59ae7a8d1252592113e20c044d885b0c7e0119250
Tx public key: d50e1a156b9b9ee8a4e99b8b61689f704f67d1b70c8de74ef39cae8579699472
Timestamp: 1708569630 Timestamp [UCT]: 2024-02-22 02:40:30 Age [y:d:h:m:s]: 00:212:17:26:25
Block: 962791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152377 RingCT/type: yes/0
Extra: 01d50e1a156b9b9ee8a4e99b8b61689f704f67d1b70c8de74ef39cae85796994720211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e166250d2d929353658ebab66fdb03690560333b7f2df4c11620069ee97cacd 0.600000000000 1422474 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": 962801, "vin": [ { "gen": { "height": 962791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e166250d2d929353658ebab66fdb03690560333b7f2df4c11620069ee97cacd" } } ], "extra": [ 1, 213, 14, 26, 21, 107, 155, 158, 232, 164, 233, 155, 139, 97, 104, 159, 112, 79, 103, 209, 183, 12, 141, 231, 78, 243, 156, 174, 133, 121, 105, 148, 114, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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