Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a5355c85c4850384e1bebfa22896ad021fe78f60bdc8f4c9417dfd09101193e

Tx prefix hash: b3b680b7b1a2291f98d0260b531a7b085e05dd2934361938cce5da2543681157
Tx public key: 2f105e042d82f4ed0ce3027935f3c4025d21dea75b1de1d6cf4805a4069f11b3
Timestamp: 1649513890 Timestamp [UCT]: 2022-04-09 14:18:10 Age [y:d:h:m:s]: 02:348:18:25:34
Block: 476597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768836 RingCT/type: yes/0
Extra: 012f105e042d82f4ed0ce3027935f3c4025d21dea75b1de1d6cf4805a4069f11b30211000000024da16a3a000000000000000000

1 output(s) for total of 16.174711159000 dcy

stealth address amount amount idx
00: be64b7ef244c081202e98d11bd63398257e7103c86e4ce763191d713b25a9764 16.174711159000 897092 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": 476607, "vin": [ { "gen": { "height": 476597 } } ], "vout": [ { "amount": 16174711159, "target": { "key": "be64b7ef244c081202e98d11bd63398257e7103c86e4ce763191d713b25a9764" } } ], "extra": [ 1, 47, 16, 94, 4, 45, 130, 244, 237, 12, 227, 2, 121, 53, 243, 196, 2, 93, 33, 222, 167, 91, 29, 225, 214, 207, 72, 5, 164, 6, 159, 17, 179, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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