Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a0eb3f0fdc564eb95ec775813865ccd8ed9bff926b1fbee8a44e37122118e8e

Tx prefix hash: 349bc0e1027ce274e653734e2d59dad08616c1782a7990a3ef8480040c824e79
Tx public key: 311da9871a11c258c08eaacc67560d07a8cb4668e1c8c50a7d1f9cbdc3f0dbbd
Timestamp: 1694388222 Timestamp [UCT]: 2023-09-10 23:23:42 Age [y:d:h:m:s]: 01:209:15:52:55
Block: 845400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410950 RingCT/type: yes/0
Extra: 01311da9871a11c258c08eaacc67560d07a8cb4668e1c8c50a7d1f9cbdc3f0dbbd02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.970150074000 dcy

stealth address amount amount idx
00: dd9433b89eb8f9f92c094b04236f470447b89324785c6f5803af76004c0e9301 0.970150074000 1298784 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": 845410, "vin": [ { "gen": { "height": 845400 } } ], "vout": [ { "amount": 970150074, "target": { "key": "dd9433b89eb8f9f92c094b04236f470447b89324785c6f5803af76004c0e9301" } } ], "extra": [ 1, 49, 29, 169, 135, 26, 17, 194, 88, 192, 142, 170, 204, 103, 86, 13, 7, 168, 203, 70, 104, 225, 200, 197, 10, 125, 31, 156, 189, 195, 240, 219, 189, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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