Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5ca1246ea0c095ba7c56f298984d2a8eba6678b371e454cf60f8e3418a7c5ca

Tx prefix hash: 657c2e06dfd1c104e718bc5b392daa0c53b3a608788857e68a9f48a9a70c1396
Tx public key: 0af458a897ebb4e92063d6cb6a757a9cbe5efad468a1b392ff80a854f8d00007
Timestamp: 1580268576 Timestamp [UCT]: 2020-01-29 03:29:36 Age [y:d:h:m:s]: 04:245:23:53:59
Block: 54803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1066321 RingCT/type: yes/0
Extra: 010af458a897ebb4e92063d6cb6a757a9cbe5efad468a1b392ff80a854f8d00007021100000025bd0f9f9f000000000000000000

1 output(s) for total of 404.031975650000 dcy

stealth address amount amount idx
00: d1182df545e84b876b417de96a0ab9c738b9770b5b2e9aa87d44e3b0757e3899 404.031975650000 101291 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": 54813, "vin": [ { "gen": { "height": 54803 } } ], "vout": [ { "amount": 404031975650, "target": { "key": "d1182df545e84b876b417de96a0ab9c738b9770b5b2e9aa87d44e3b0757e3899" } } ], "extra": [ 1, 10, 244, 88, 168, 151, 235, 180, 233, 32, 99, 214, 203, 106, 117, 122, 156, 190, 94, 250, 212, 104, 161, 179, 146, 255, 128, 168, 84, 248, 208, 0, 7, 2, 17, 0, 0, 0, 37, 189, 15, 159, 159, 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