Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27a86a5a4ebdc08adc0d9db13c6104572b18fecb5cdd7c61af1760c0b6ef3aba

Tx prefix hash: 8d8de374ec87ac38a6bbd5b0ba026176c1dcccc2fbfaa554ff9644662a585a70
Tx public key: 362058e18578da6d3a3697230b3060cc8332adb82aa546f9296fe831cffc0f5f
Timestamp: 1577764911 Timestamp [UCT]: 2019-12-31 04:01:51 Age [y:d:h:m:s]: 05:005:20:15:01
Block: 35454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154207 RingCT/type: yes/0
Extra: 01362058e18578da6d3a3697230b3060cc8332adb82aa546f9296fe831cffc0f5f021100000003e39b962a000000000000000000

1 output(s) for total of 468.311182126000 dcy

stealth address amount amount idx
00: 4f2343897c7d5fe1551f46fcaa489a825f72e374e565fded17cc6dc0e2445b7e 468.311182126000 59803 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": 35464, "vin": [ { "gen": { "height": 35454 } } ], "vout": [ { "amount": 468311182126, "target": { "key": "4f2343897c7d5fe1551f46fcaa489a825f72e374e565fded17cc6dc0e2445b7e" } } ], "extra": [ 1, 54, 32, 88, 225, 133, 120, 218, 109, 58, 54, 151, 35, 11, 48, 96, 204, 131, 50, 173, 184, 42, 165, 70, 249, 41, 111, 232, 49, 207, 252, 15, 95, 2, 17, 0, 0, 0, 3, 227, 155, 150, 42, 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