Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 125233e77099a74e9e3e0cc4869bf9245aa0cbe5934992348c8a59c6cf99db97

Tx prefix hash: e62023c2a56f55d3015cc7e6442d374e4d1d55c5013efe867c32af3f406806de
Tx public key: 4a1f6e008fae6d0a766cbab9c7a1e58bf2724ccc99a1e222f77869195a1ea0a6
Timestamp: 1697317161 Timestamp [UCT]: 2023-10-14 20:59:21 Age [y:d:h:m:s]: 01:178:14:57:30
Block: 869707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388692 RingCT/type: yes/0
Extra: 014a1f6e008fae6d0a766cbab9c7a1e58bf2724ccc99a1e222f77869195a1ea0a602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.805934420000 dcy

stealth address amount amount idx
00: a675f445d63b95b7bc0f5e111da8dff71e9fc291a1f5ca9453cfc20c80bb4a2f 0.805934420000 1324562 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": 869717, "vin": [ { "gen": { "height": 869707 } } ], "vout": [ { "amount": 805934420, "target": { "key": "a675f445d63b95b7bc0f5e111da8dff71e9fc291a1f5ca9453cfc20c80bb4a2f" } } ], "extra": [ 1, 74, 31, 110, 0, 143, 174, 109, 10, 118, 108, 186, 185, 199, 161, 229, 139, 242, 114, 76, 204, 153, 161, 226, 34, 247, 120, 105, 25, 90, 30, 160, 166, 2, 17, 0, 0, 0, 5, 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