Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db7e5fd10827244584a030c0c92c021a5cfbace6e27965f6fab66be3c716b977

Tx prefix hash: 57d178e43be0687501a5efcda733fd04786ed275f59e035a3b6fb602bcf7cc9c
Tx public key: 19b81e8c634d4dc751b31e367cb8d636825d1a869f9833f1b28761a04bbb89fb
Timestamp: 1577815014 Timestamp [UCT]: 2019-12-31 17:56:54 Age [y:d:h:m:s]: 05:040:15:18:11
Block: 35924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178765 RingCT/type: yes/0
Extra: 0119b81e8c634d4dc751b31e367cb8d636825d1a869f9833f1b28761a04bbb89fb021100000007ac34bf9e000000000000000000

1 output(s) for total of 466.626854396000 dcy

stealth address amount amount idx
00: f02353ab88f504ea488af2a138d35af2a7cfe7a10f4ec75af9686342c94a73e7 466.626854396000 60682 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": 35934, "vin": [ { "gen": { "height": 35924 } } ], "vout": [ { "amount": 466626854396, "target": { "key": "f02353ab88f504ea488af2a138d35af2a7cfe7a10f4ec75af9686342c94a73e7" } } ], "extra": [ 1, 25, 184, 30, 140, 99, 77, 77, 199, 81, 179, 30, 54, 124, 184, 214, 54, 130, 93, 26, 134, 159, 152, 51, 241, 178, 135, 97, 160, 75, 187, 137, 251, 2, 17, 0, 0, 0, 7, 172, 52, 191, 158, 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