Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3385f510c574ad3e936a4e93a4accb38f799ed5162c0565ff3acbdfff8658b9d

Tx prefix hash: 481c39447c33beeba2d9f6d48a55778271a17dd3e1a6651bc335ae990ef95bcb
Tx public key: 0a46cabe6810498a00e2edf4e3fbc54910274215791391ad3cc7a689fb25bbe5
Timestamp: 1709093994 Timestamp [UCT]: 2024-02-28 04:19:54 Age [y:d:h:m:s]: 00:331:13:59:32
Block: 967142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237308 RingCT/type: yes/0
Extra: 010a46cabe6810498a00e2edf4e3fbc54910274215791391ad3cc7a689fb25bbe502110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6a83c11593a6cb37f101fc7c9ab7cb340e8f6a6c39641516b1b4b2b02635d4b 0.600000000000 1426913 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": 967152, "vin": [ { "gen": { "height": 967142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6a83c11593a6cb37f101fc7c9ab7cb340e8f6a6c39641516b1b4b2b02635d4b" } } ], "extra": [ 1, 10, 70, 202, 190, 104, 16, 73, 138, 0, 226, 237, 244, 227, 251, 197, 73, 16, 39, 66, 21, 121, 19, 145, 173, 60, 199, 166, 137, 251, 37, 187, 229, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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