Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d06894e322e4efffeacc8b90f35f06ee2bbaff6e203aa764389aa9165e080b4c

Tx prefix hash: 972ca47a20c1fbcef971a0923dacced3bf8c0f1cdcb906950283487378fff2d3
Tx public key: 2d031818b93bb31ce8c3a80126a6d06f792297ad493d4d496e9032bdd0453fe4
Timestamp: 1708214345 Timestamp [UCT]: 2024-02-17 23:59:05 Age [y:d:h:m:s]: 01:126:08:39:01
Block: 959842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351186 RingCT/type: yes/0
Extra: 012d031818b93bb31ce8c3a80126a6d06f792297ad493d4d496e9032bdd0453fe40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cd55d27143da4f3c4fc09f1b5b4a63c101ecd38d8877ec9d8e2cc1d0c536064 0.600000000000 1419401 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": 959852, "vin": [ { "gen": { "height": 959842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cd55d27143da4f3c4fc09f1b5b4a63c101ecd38d8877ec9d8e2cc1d0c536064" } } ], "extra": [ 1, 45, 3, 24, 24, 185, 59, 179, 28, 232, 195, 168, 1, 38, 166, 208, 111, 121, 34, 151, 173, 73, 61, 77, 73, 110, 144, 50, 189, 208, 69, 63, 228, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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