Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1675f22b0feb957b251fb78b5a361a0524169812f89da040c8144ce485798b6

Tx prefix hash: 4a74b8106b811f1e75818a07c2f6b77d15f199f38745ddd2d5669ac412dd22b4
Tx public key: d808958e90f37cf3b0fe64f2f89695d5d0b38e8212c42b38347d85835a4989d7
Timestamp: 1723794925 Timestamp [UCT]: 2024-08-16 07:55:25 Age [y:d:h:m:s]: 01:170:06:23:46
Block: 1089017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380089 RingCT/type: yes/0
Extra: 01d808958e90f37cf3b0fe64f2f89695d5d0b38e8212c42b38347d85835a4989d7021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44006d754d63dd9ffe201ed796a851a4b5c7e243cb6c04619dd52c0ea49aae4d 0.600000000000 1563636 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": 1089027, "vin": [ { "gen": { "height": 1089017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44006d754d63dd9ffe201ed796a851a4b5c7e243cb6c04619dd52c0ea49aae4d" } } ], "extra": [ 1, 216, 8, 149, 142, 144, 243, 124, 243, 176, 254, 100, 242, 248, 150, 149, 213, 208, 179, 142, 130, 18, 196, 43, 56, 52, 125, 133, 131, 90, 73, 137, 215, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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