Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689b4758943614b1acbb8dd1d7eb4c38c3599b0e58fc31dde82935a541361595

Tx prefix hash: 51ba516ae8d3856f34f1059214ad362736034383e626923574dd4d76d520f8ec
Tx public key: 941aba9a1ab3f81878718dcc9aa6edeb6c4d746a6d2bbe7e8d011ac8461756bf
Timestamp: 1674734610 Timestamp [UCT]: 2023-01-26 12:03:30 Age [y:d:h:m:s]: 02:311:16:29:59
Block: 683164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742150 RingCT/type: yes/0
Extra: 01941aba9a1ab3f81878718dcc9aa6edeb6c4d746a6d2bbe7e8d011ac8461756bf021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.344983741000 dcy

stealth address amount amount idx
00: e4039f3e13f1cb17c9fc36b540ce83bc7d930934a4cface79994b30ed54a788d 3.344983741000 1125335 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": 683174, "vin": [ { "gen": { "height": 683164 } } ], "vout": [ { "amount": 3344983741, "target": { "key": "e4039f3e13f1cb17c9fc36b540ce83bc7d930934a4cface79994b30ed54a788d" } } ], "extra": [ 1, 148, 26, 186, 154, 26, 179, 248, 24, 120, 113, 141, 204, 154, 166, 237, 235, 108, 77, 116, 106, 109, 43, 190, 126, 141, 1, 26, 200, 70, 23, 86, 191, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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