Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ddec988f8995b085b359f56b3f72473dd93aa5c96b536ab8ca4e11ac261a3f9

Tx prefix hash: 237b6956aeee7a4ff208ef7fde6b6ad51315fbeb2842cbb4824dd9dd4621ad85
Tx public key: 628c435b7e9a4b9af68950f6824bbdf9e63b84dbe5430215fc70923424ab2bd6
Timestamp: 1700898928 Timestamp [UCT]: 2023-11-25 07:55:28 Age [y:d:h:m:s]: 01:090:08:16:56
Block: 899190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325699 RingCT/type: yes/0
Extra: 01628c435b7e9a4b9af68950f6824bbdf9e63b84dbe5430215fc70923424ab2bd602110000000233af99f4000000000000000000

1 output(s) for total of 0.643591416000 dcy

stealth address amount amount idx
00: a4e21b1acedbe6271b2f335c8d86ba39e8db366818d557fe468e0eb24d37ee5b 0.643591416000 1355633 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": 899200, "vin": [ { "gen": { "height": 899190 } } ], "vout": [ { "amount": 643591416, "target": { "key": "a4e21b1acedbe6271b2f335c8d86ba39e8db366818d557fe468e0eb24d37ee5b" } } ], "extra": [ 1, 98, 140, 67, 91, 126, 154, 75, 154, 246, 137, 80, 246, 130, 75, 189, 249, 230, 59, 132, 219, 229, 67, 2, 21, 252, 112, 146, 52, 36, 171, 43, 214, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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