Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e853f9306921eea07feaa9a8d7309a4f64201cb4f7d31c76b5d8fc637cd388

Tx prefix hash: 5cbfda3635721eba926b0a21c7047117761309a0404c2576f10cff3fd8679c4a
Tx public key: 9f2acbffaa8987fa40ba5b6fa6d54e3b283c7e36fdaf6e55b337bdbdbf4bfdb0
Timestamp: 1639099213 Timestamp [UCT]: 2021-12-10 01:20:13 Age [y:d:h:m:s]: 03:028:19:46:52
Block: 392155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799552 RingCT/type: yes/0
Extra: 019f2acbffaa8987fa40ba5b6fa6d54e3b283c7e36fdaf6e55b337bdbdbf4bfdb0021100000002b494d89c000000000000000000

1 output(s) for total of 30.806025421000 dcy

stealth address amount amount idx
00: e41a32a9d2deaa689c71bbf6419a2e7406512ad64f08f5f72fc14f034261eab6 30.806025421000 788920 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": 392165, "vin": [ { "gen": { "height": 392155 } } ], "vout": [ { "amount": 30806025421, "target": { "key": "e41a32a9d2deaa689c71bbf6419a2e7406512ad64f08f5f72fc14f034261eab6" } } ], "extra": [ 1, 159, 42, 203, 255, 170, 137, 135, 250, 64, 186, 91, 111, 166, 213, 78, 59, 40, 60, 126, 54, 253, 175, 110, 85, 179, 55, 189, 189, 191, 75, 253, 176, 2, 17, 0, 0, 0, 2, 180, 148, 216, 156, 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