Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e8ebcbc09f3b387bba51f2c6cc7c5a84ecc8bec6b2de842dc26f81b406d9bf5

Tx prefix hash: cd8229bb4054ef4461e668f9836bb21f3d519f7cda44387494a0068f7b9958e1
Tx public key: 260a350f99c202b6bf92dd708c6997f8f045de9183237fc73f06674f69d50a6f
Timestamp: 1724938497 Timestamp [UCT]: 2024-08-29 13:34:57 Age [y:d:h:m:s]: 00:252:10:58:16
Block: 1098502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180295 RingCT/type: yes/0
Extra: 01260a350f99c202b6bf92dd708c6997f8f045de9183237fc73f06674f69d50a6f02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 284f48567894079ed738c6b3d903a024ab4fb5f63d3da4692e0ac4e58c2e52aa 0.600000000000 1574239 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": 1098512, "vin": [ { "gen": { "height": 1098502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "284f48567894079ed738c6b3d903a024ab4fb5f63d3da4692e0ac4e58c2e52aa" } } ], "extra": [ 1, 38, 10, 53, 15, 153, 194, 2, 182, 191, 146, 221, 112, 140, 105, 151, 248, 240, 69, 222, 145, 131, 35, 127, 199, 63, 6, 103, 79, 105, 213, 10, 111, 2, 17, 0, 0, 0, 6, 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