Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785d3a0466d5cfa5b998d19dca620b6d6db0c1b772fdc9cf815ccbd9ceb1935e

Tx prefix hash: 75297f00a7460d3ce51d30bb0834dde18f52e7bce53d267c7801270e307cd9d6
Tx public key: feb3b65f26aceb9e94ab9548d021b4688781037fc930fa9f277c27ba07f877a6
Timestamp: 1711031667 Timestamp [UCT]: 2024-03-21 14:34:27 Age [y:d:h:m:s]: 01:014:19:35:31
Block: 983226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271542 RingCT/type: yes/0
Extra: 01feb3b65f26aceb9e94ab9548d021b4688781037fc930fa9f277c27ba07f877a602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e60b69a5d3d72765b29ea7521a07999f8a5cf3ca3accb5efbe2050b0d4a02c57 0.600000000000 1443353 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": 983236, "vin": [ { "gen": { "height": 983226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e60b69a5d3d72765b29ea7521a07999f8a5cf3ca3accb5efbe2050b0d4a02c57" } } ], "extra": [ 1, 254, 179, 182, 95, 38, 172, 235, 158, 148, 171, 149, 72, 208, 33, 180, 104, 135, 129, 3, 127, 201, 48, 250, 159, 39, 124, 39, 186, 7, 248, 119, 166, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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