Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a173e85569694f14dcc0218c59425e63fc2a9784f08955c8f5cecf4ae9b909a1

Tx prefix hash: 57a4dd7cc469d2e16800f74c660d7014346b92d1dff4caec4fe3659090da50e5
Tx public key: 3c8642d727853c3806f9b0d3581b600f4b187e9d3290cbf4a9559b7afc6c015d
Timestamp: 1706881169 Timestamp [UCT]: 2024-02-02 13:39:29 Age [y:d:h:m:s]: 01:053:01:06:42
Block: 948785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298954 RingCT/type: yes/0
Extra: 013c8642d727853c3806f9b0d3581b600f4b187e9d3290cbf4a9559b7afc6c015d02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 041d65b85575952b95ce02d7aab84177eb9538213e86f0ca5addb921659b4c27 0.600000000000 1407267 of 15

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": 948795, "vin": [ { "gen": { "height": 948785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "041d65b85575952b95ce02d7aab84177eb9538213e86f0ca5addb921659b4c27" } } ], "extra": [ 1, 60, 134, 66, 215, 39, 133, 60, 56, 6, 249, 176, 211, 88, 27, 96, 15, 75, 24, 126, 157, 50, 144, 203, 244, 169, 85, 155, 122, 252, 108, 1, 93, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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