Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 555c4b109b4009852db65d410d66d36966479d275f891ae057b24cff3f965ba1

Tx prefix hash: 2e39278154b3aec4657a3826d4900afce3b162cae7fef23eda1f23efe247936f
Tx public key: 0767dde3ae956ffa6dab35bdd2ea91d39a8264496ed5d192f4ef0aade024104b
Timestamp: 1651411193 Timestamp [UCT]: 2022-05-01 13:19:53 Age [y:d:h:m:s]: 02:204:01:01:10
Block: 492103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 665774 RingCT/type: yes/0
Extra: 010767dde3ae956ffa6dab35bdd2ea91d39a8264496ed5d192f4ef0aade024104b0211000000012e6b1fd5000000000000000000

1 output(s) for total of 14.370063803000 dcy

stealth address amount amount idx
00: 765cfa3e0bfeb694735d9f0fec8e2aa38fe0d5d5a5180aeac61d36015e1941b4 14.370063803000 915380 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": 492113, "vin": [ { "gen": { "height": 492103 } } ], "vout": [ { "amount": 14370063803, "target": { "key": "765cfa3e0bfeb694735d9f0fec8e2aa38fe0d5d5a5180aeac61d36015e1941b4" } } ], "extra": [ 1, 7, 103, 221, 227, 174, 149, 111, 250, 109, 171, 53, 189, 210, 234, 145, 211, 154, 130, 100, 73, 110, 213, 209, 146, 244, 239, 10, 173, 224, 36, 16, 75, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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