Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90f942b70293c147b09403e722374a3abd33e9d6c20a098825d32f9bd8cc1617

Tx prefix hash: 206160c2a2f67f5cfa07081fc08509d5adcb68ed46a4f55a2cebb6e4162f454e
Tx public key: b593a3c5b8847534940a8aabda9d4861aeb42d29f715455856653feb61735829
Timestamp: 1716146811 Timestamp [UCT]: 2024-05-19 19:26:51 Age [y:d:h:m:s]: 00:324:18:53:51
Block: 1025609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232144 RingCT/type: yes/0
Extra: 01b593a3c5b8847534940a8aabda9d4861aeb42d29f715455856653feb6173582902110000000352d47e94000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: a595d3a03afe09ea8f80fa8b25fb0a6d8e73c83c1b055a1a21fb177d9bcd64ff 0.615610000000 1492234 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": 1025619, "vin": [ { "gen": { "height": 1025609 } } ], "vout": [ { "amount": 615610000, "target": { "key": "a595d3a03afe09ea8f80fa8b25fb0a6d8e73c83c1b055a1a21fb177d9bcd64ff" } } ], "extra": [ 1, 181, 147, 163, 197, 184, 132, 117, 52, 148, 10, 138, 171, 218, 157, 72, 97, 174, 180, 45, 41, 247, 21, 69, 88, 86, 101, 63, 235, 97, 115, 88, 41, 2, 17, 0, 0, 0, 3, 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