Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb0eb2aa11a7e6de33c64a5d885e23451c84018cacf334015b7e411a663213ab

Tx prefix hash: 07d3588dca68a7a80523fd9480da54255c0aa343ee96a8543ba21bb409646289
Tx public key: f4408848661f3e11e5560b6291cf3b85f0e4079af2f10cf75b3dd0ef3e06e6c3
Timestamp: 1673811386 Timestamp [UCT]: 2023-01-15 19:36:26 Age [y:d:h:m:s]: 02:003:03:00:51
Block: 675488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524126 RingCT/type: yes/0
Extra: 01f4408848661f3e11e5560b6291cf3b85f0e4079af2f10cf75b3dd0ef3e06e6c30211000000018b7b6602000000000000000000

1 output(s) for total of 3.546727292000 dcy

stealth address amount amount idx
00: 8b2883f103c46647b4cbae516ff8ff3d3a5686245774808ea4153f5fa24f89c9 3.546727292000 1117167 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": 675498, "vin": [ { "gen": { "height": 675488 } } ], "vout": [ { "amount": 3546727292, "target": { "key": "8b2883f103c46647b4cbae516ff8ff3d3a5686245774808ea4153f5fa24f89c9" } } ], "extra": [ 1, 244, 64, 136, 72, 102, 31, 62, 17, 229, 86, 11, 98, 145, 207, 59, 133, 240, 228, 7, 154, 242, 241, 12, 247, 91, 61, 208, 239, 62, 6, 230, 195, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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