Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3872fbf61bd1a860d8bf2b3468a57d138937a5449e42f44491a66397bfbb4e

Tx prefix hash: 41d57ab6a09e87e660c20b4869313a35d189f4cd079ce46b19cac80a4afe7f13
Tx public key: 0c1443a07f2e2689860eb410783cd870555f50845d5bc2ce7b143cf8ca110d54
Timestamp: 1699348480 Timestamp [UCT]: 2023-11-07 09:14:40 Age [y:d:h:m:s]: 01:179:23:03:18
Block: 886346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389827 RingCT/type: yes/0
Extra: 010c1443a07f2e2689860eb410783cd870555f50845d5bc2ce7b143cf8ca110d5402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.709851927000 dcy

stealth address amount amount idx
00: 41d22fce5d1b744e52cf9dcded81317c23585c7f4256f2ecb5ddd936b77d6466 0.709851927000 1342161 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": 886356, "vin": [ { "gen": { "height": 886346 } } ], "vout": [ { "amount": 709851927, "target": { "key": "41d22fce5d1b744e52cf9dcded81317c23585c7f4256f2ecb5ddd936b77d6466" } } ], "extra": [ 1, 12, 20, 67, 160, 127, 46, 38, 137, 134, 14, 180, 16, 120, 60, 216, 112, 85, 95, 80, 132, 93, 91, 194, 206, 123, 20, 60, 248, 202, 17, 13, 84, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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