Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3627f1e19ec28c879c6f444f40a47e32c797cf597cc9a7aa066430beb7f9f0f1

Tx prefix hash: 661a09ba9e71e3fceb5a6671a26dd4481efd1d14f36d2a8d39468f51f9084364
Tx public key: 141ad94d8b2aeb30d12dbc1272d0383584014a9d6f6ef8bffc1380496b917274
Timestamp: 1676187844 Timestamp [UCT]: 2023-02-12 07:44:04 Age [y:d:h:m:s]: 01:337:23:51:21
Block: 695216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502518 RingCT/type: yes/0
Extra: 01141ad94d8b2aeb30d12dbc1272d0383584014a9d6f6ef8bffc1380496b91727402110000000175e3f0e9000000000000000000

1 output(s) for total of 3.051130016000 dcy

stealth address amount amount idx
00: 297702ead8b5769ca64d69a22d1addba54e6f076502bd6d729c5736977199077 3.051130016000 1138167 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": 695226, "vin": [ { "gen": { "height": 695216 } } ], "vout": [ { "amount": 3051130016, "target": { "key": "297702ead8b5769ca64d69a22d1addba54e6f076502bd6d729c5736977199077" } } ], "extra": [ 1, 20, 26, 217, 77, 139, 42, 235, 48, 209, 45, 188, 18, 114, 208, 56, 53, 132, 1, 74, 157, 111, 110, 248, 191, 252, 19, 128, 73, 107, 145, 114, 116, 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