Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 343547064c6ca63bec6fbc2e5cd453eb2ba8d17c3b874078f022d70cfd33a85a

Tx prefix hash: 1d7f2a0282d725fa4eb91e42d43d63c9f7883a6de65224f24b16468b750fddb0
Tx public key: fe975346e061b27501ac51d915a876b6fd4ad8cbe61199899d2e504f85d26dd2
Timestamp: 1723558235 Timestamp [UCT]: 2024-08-13 14:10:35 Age [y:d:h:m:s]: 00:224:20:50:35
Block: 1087056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160568 RingCT/type: yes/0
Extra: 01fe975346e061b27501ac51d915a876b6fd4ad8cbe61199899d2e504f85d26dd202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 208f9227cf2f3dd49654a298c0ed54558ecf8a5e61c94e6c52b63cc9a746aee2 0.600000000000 1561661 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": 1087066, "vin": [ { "gen": { "height": 1087056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "208f9227cf2f3dd49654a298c0ed54558ecf8a5e61c94e6c52b63cc9a746aee2" } } ], "extra": [ 1, 254, 151, 83, 70, 224, 97, 178, 117, 1, 172, 81, 217, 21, 168, 118, 182, 253, 74, 216, 203, 230, 17, 153, 137, 157, 46, 80, 79, 133, 210, 109, 210, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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