Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe93d6ff0e20bf0e1df2e3ddffc6d42534b92d7c2189365f1e7457356cd6e07f

Tx prefix hash: a73f9c564b69917c21e66576b919acbc63fa6de1ab3856690580f0f7310f5f2f
Tx public key: 402e6cb53eb1e7dceb296800be451fcece7e851050049c08c06a53bd4a5ab96a
Timestamp: 1702686434 Timestamp [UCT]: 2023-12-16 00:27:14 Age [y:d:h:m:s]: 01:335:12:33:05
Block: 914009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498662 RingCT/type: yes/0
Extra: 01402e6cb53eb1e7dceb296800be451fcece7e851050049c08c06a53bd4a5ab96a02110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 386124800f1752a3dc34491d8a04fa5cce041950c0f3a6756c7c8eef65e0b226 0.600000000000 1371289 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": 914019, "vin": [ { "gen": { "height": 914009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "386124800f1752a3dc34491d8a04fa5cce041950c0f3a6756c7c8eef65e0b226" } } ], "extra": [ 1, 64, 46, 108, 181, 62, 177, 231, 220, 235, 41, 104, 0, 190, 69, 31, 206, 206, 126, 133, 16, 80, 4, 156, 8, 192, 106, 83, 189, 74, 90, 185, 106, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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