Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1592611a1d39777c4a36afb0d5b8bfdb5170b272d19a35ac13c796c392a1ab57

Tx prefix hash: db7e4e6295f313fa7792a09fff5bc55c98ff35a834c38380b07cb2788f763f5e
Tx public key: 3583203a7ab3a3add01f5e1fb72225b9ebbb19b61c04bd0c2fdb2058d7ac3175
Timestamp: 1632325405 Timestamp [UCT]: 2021-09-22 15:43:25 Age [y:d:h:m:s]: 03:254:23:11:43
Block: 338885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 958245 RingCT/type: yes/0
Extra: 013583203a7ab3a3add01f5e1fb72225b9ebbb19b61c04bd0c2fdb2058d7ac31750211000000128d0de867000000000000000000

1 output(s) for total of 46.252344414000 dcy

stealth address amount amount idx
00: babd6d13821ab14c7e32359275b5a4ffcc2df60f8740c6d5c3a9aecd4e3696b7 46.252344414000 697236 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": 338895, "vin": [ { "gen": { "height": 338885 } } ], "vout": [ { "amount": 46252344414, "target": { "key": "babd6d13821ab14c7e32359275b5a4ffcc2df60f8740c6d5c3a9aecd4e3696b7" } } ], "extra": [ 1, 53, 131, 32, 58, 122, 179, 163, 173, 208, 31, 94, 31, 183, 34, 37, 185, 235, 187, 25, 182, 28, 4, 189, 12, 47, 219, 32, 88, 215, 172, 49, 117, 2, 17, 0, 0, 0, 18, 141, 13, 232, 103, 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